View PM7381-PI_2461211.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra , inc., and for its customers? internal use pm7381 freedm?-32a672 frame engine and datalink manager 32a672 data sheet proprietary and confidential issue 6: august 2001
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use i public revision history issue no. issue date details of change issue 1 february 20, 2000 created document. issue 2 may 30, 1999 added pinout. issue 3 january, 2000 minor changes. issue 4 june 2000 minor corrections and changes to some dc and ac timing parameters. issue 5 october 2000 re-issue for minor corrections to mechanical drawing and design summary sections. because the changes are so few, change bars have been kept to show both issue 4 and issue 5 changes. issue 6 august 2001 patent information included in legal footer. change bars reflect issue 5.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use ii contents 1 features...............................................................................................1 2 applications ........................................................................................4 3 references .........................................................................................5 4 block diagram....................................................................................6 5 description .........................................................................................7 6 pin diagram ........................................................................................ 11 7 pin description ................................................................................12 8 functional description................................................................43 8.1 high speed multi-vendor integration protocol (h-mvip) ......................................................................................43 8.2 high-level data link control (hdlc) protocol.........43 8.3 receive channel assigner ................................................44 8.3.1 line interface translator (lit) .......................................46 8.3.2 line interface .................................................................47 8.3.3 priority encoder .............................................................47 8.3.4 channel assigner ..........................................................48 8.3.5 loopback controller.......................................................48 8.4 receive hdlc processor / partial packet buffer ...48 8.4.1 hdlc processor............................................................49 8.4.2 partial packet buffer processor .....................................49 8.5 receive any-phy interface ................................................51 8.5.1 fifo storage and control..............................................52
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use iii 8.5.2 polling control and management...................................53 8.6 transmit any-phy interface .............................................53 8.6.1 fifo storage and control..............................................53 8.6.2 polling control and management...................................55 8.7 transmit hdlc controller / partial packet buffer56 8.7.1 transmit hdlc processor .............................................56 8.7.2 transmit partial packet buffer processor ......................57 8.8 transmit channel assigner..............................................59 8.8.1 line interface translator (lit) .......................................61 8.8.2 line interface .................................................................61 8.8.3 priority encoder .............................................................62 8.8.4 channel assigner ..........................................................62 8.9 performance monitor .......................................................63 8.10 jtag test access port interface...................................63 8.11 microprocesso r interface .............................................63 9 normal mode register description ........................................66 9.1 microprocessor accessible registers .....................66 10 test features description .......................................................155 10.1 test mode registers.........................................................155 10.2 jtag test port .....................................................................156 10.2.1 identification register ..................................................157 10.2.2 boundary scan register ..............................................157 11 operations.......................................................................................175 11.1 toctl connections ............................................................175
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use iv 11.2 jtag support........................................................................175 12 functional timing..........................................................................182 12.1 receive h-mvip link timing ...............................................182 12.2 transmit h-mvip link timing .............................................183 12.3 receive non h-mvip link timing.......................................184 12.4 transmit non h-mvip link timing ....................................186 12.5 receive appi timing .............................................................187 12.6 transmit appi timing ..........................................................191 12.7 bert interface.....................................................................194 13 absolute maximum ratings........................................................196 14 d.c. charact eristics....................................................................197 15 freedm-32a672 timing characteristics .................................199 16 ordering and thermal information ......................................213 17 mechanical information.............................................................214
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use v list of figures figure 1 ? h-mvip protocol.....................................................................43 figure 2 ? hdlc frame...............................................................................44 figure 3 ? crc generator.......................................................................44 figure 4 ? partial pa cket buffer structure ..................................50 figure 5 ? partial pa cket buffer structure ..................................57 figure 6 ? input observation cell (in_cell) ...................................171 figure 7 ? output cell (out_cell)......................................................172 figure 8 ? bi-directional cell (io_cell)............................................173 figure 9 ? layout of output enable and bi-directional cells174 figure 10 ? boundary sc an archite cture ......................................176 figure 11 ? tap controller finite state machine.........................178 figure 12 ? receive 8.192 mbps h-mvip link timing .........................182 figure 13 ? receive 2.048 mbps h-mvip link timing .........................183 figure 14 ? transmit 8.192 mbps h-mvip link timing .......................183 figure 15 ? transmit 2.048 mbps h-mvip link timing .......................184 figure 16 ? unchannelised receive link timing ............................185 figure 17 ? channelised t1/j1 receive link timing........................185 figure 18 ? channelised e1 receive link timing ............................186 figure 19 ? unchannelised transmit link timing ..........................186 figure 20 ? channelised t1/j1 transmit link timing .....................187 figure 21 ? channelised e1 transmit link timing..........................187 figure 22 ? receive appi timing (normal transfer) .....................188
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use vi figure 23 ? receive appi timing (auto deselection) ....................189 figure 24 ? receive appi timing (optimal reselection)...............190 figure 25 ? receive appi timing (boundary condition) ...............191 figure 26 ? transmit appi timi ng (normal transfer)...................192 figure 27 ? transmit appi timing (special conditions)................193 figure 28 ? transmit appi timing (polling).......................................194 figure 29 ? receive bert port timing................................................195 figure 30 ? transmit bert port timing .............................................195 figure 31 ? receive data & frame pulse timing (2.048 mbps h-mvip mode) ..................................................................................................201 figure 32 ? receive data & frame pulse timing (8.192 mbps h-mvip mode) ..................................................................................................201 figure 33 ? receive data timing (non h-mvip mode).......................202 figure 34 ? bert input timing ...............................................................202 figure 35 ? transmit data & frame pulse timing (2.048 mbps h- mvip mode) ........................................................................................204 figure 36 ? transmit data & frame pulse timing (8.192 mbps h- mvip mode) ........................................................................................205 figure 37 ? transmit data timing (non h-mvip mode) ....................205 figure 38 ? bert output timing ...........................................................206 figure 39 ? receive any-phy packet interface timing.................207 figure 40 ? transmit any-phy packet interface timing ..............208 figure 41 ? microprocessor read access timing .......................209 figure 42 ? microprocessor write access timing...................... 211 figure 43 ? jtag port interface timing............................................212 figure 44 ? 329 pin plastic ball grid array (pbga)........................214
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use vii list of tables table 1 ? line side interface signals (154) ........................................12 table 2 ? any-phy packet interface signals (70) .............................22 table 3 ? microprocessor interface signals (31).........................34 table 4 ? miscellaneous in terface signals (9) ...............................36 table 5 ? production test interface signals (0 - multiplexed) 38 table 6 ? power and ground signals (65)..........................................39 table 7 ? transmit polling......................................................................55 table 8 ? normal mode microprocessor accessible registers ................................................................................................................63 table 9 ? receive links #0 to #2 configuration ...............................98 table 10 ? receive links #3 to #31 configuration ...........................99 table 11 ? crc[1:0] settings ...................................................................106 table 12 ? crc[1:0] settings................................................................... 117 table 13 ? flag[2:0] settings .................................................................122 table 14 ? level[3:0]/trans settings ..................................................124 table 15 ? transmit links #0 to #2 configuration ........................139 table 16 ? transmit links #3 to #31 configuration.......................140 table 17 ? test mode register memory map...................................156 table 18 ? instruction register.........................................................157 table 19 ? boundary scan chain .........................................................157 table 20 ? freedm?toctl connections ............................................175 table 21 ? freedm-32a672 absolute maximum ratings .................196 table 22 ? freedm-32a672 d.c. characteristics .............................197
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use viii table 23 ? freedm-32a672 link input (figure 31 to figure 34) ....199 table 24 ? freedm-32a672 link output (figure 35 to figure 38) 202 table 25 ? any-phy packet interface (figure 39 to figure 40) ..206 table 26 ? microprocessor interface read access (figure 41) ..............................................................................................................208 table 27 ? microprocessor interface write access (figure 42) ..............................................................................................................210 table 28 ? jtag port interface (figure 43)...................................... 211 table 29 ? freedm-32a672 ordering information..........................213 table 30 ? freedm-32a672 thermal information ............................213
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 1 1 features single-chip multi-channel hdlc controller with a 50 mhz, 16 bit ?any-phy? packet interface (appi) for transfer of packet data using an external controller. supports up to 672 bi-directional hdlc channels assigned to a maximum of 32 h-mvip digital telephony buses at 2.048 mbps per link. the links are grouped into 4 logical groups of 8 links. a common clock and a type 0 frame pulse is shared among links in each logical group. the number of time-slots assigned to an hdlc channel is programmable from 1 to 32. supports up to 672 bi-directional hdlc channels assigned to a maximum of 8 h-mvip digital telephony buses at 8.192 mbps per link. the links share a common clock and a type 0 frame pulse. the number of time-slots assigned to an hdlc channel is programmable from 1 to 128. supports up to 672 bi-directional hdlc channels assigned to a maximum of 32 channelised t1/j1 or e1 links. the number of time-slots assigned to an hdlc channel is programmable from 1 to 24 (for t1/j1) and from 1 to 31 (for e1). supports up to 32 bi-directional hdlc channels each assigned to an unchannelised arbitrary rate link, subject to a maximum aggregate link clock rate of 64 mhz in each direction. channels assigned to links 0 to 2 support a clock rate of up to 51.84 mhz. channels assigned to links 3 to 31 support a clock rate of up to 10 mhz. supports three bi-directional hdlc channels each assigned to an unchannelised arbitrary rate link of up to 51.84 mhz when sysclk is running at 45 mhz. supports a mix of up to 32 channelised, unchannelised and h-mvip links, subject to the constraint of a maximum of 672 channels and a maximum aggregate link clock rate of 64 mhz in each direction. links configured for channelised t1/j1/e1 or unchannelised operation support the gapped-clock method for determining time-slots which is backwards compatible with the freedm-8 and freedm-32 devices. for each channel, the hdlc receiver supports programmable flag sequence detection, bit de-stuffing and frame check sequence validation. the receiver
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 2 supports the validation of both crc-ccitt and crc-32 frame check sequences. for each channel, the receiver che cks for packet abort sequences, octet aligned packet length and for minimum and maximum packet length. the receiver supports filtering of packets that are larger than a user specified maximum value. alternatively, for each channel, the receiver supports a transparent mode where each octet is transferred transparently on the receive appi. for channelised links, the octets are aligned with the receive time-slots. for each channel, time-slots are selectable to be in 56 kbits/s format or 64 kbits/s clear channel format. for each channel, the hdlc transmitter supports programmable flag sequence generation, bit stuffing and frame check sequence generation. the transmitter supports the generati on of both crc-ccitt and crc-32 frame check sequences. the transmitter also aborts packets under the direction of the external controller or automatically when the channel underflows. alternatively, for each channel, the transmitter supports a transparent mode where each octet is inserted transparently from the transmit appi. for channelised links, the octets are aligned with the transmit time-slots. supports per-channel configurable appi burst sizes of up to 256 bytes for transfers of packet data. provides 32 kbytes of on-chip memory for partial packet buffering in both the transmit and the receive directions. this memory may be configured to support a variety of different channel configurations from a single channel with 32 kbytes of buffering to 672 channels, each with a minimum of 48 bytes of buffering. provides a 16 bit microprocessor interface for configuration and status monitoring. provides a standard 5 signal p1149.1 jtag test port for boundary scan board test purposes. supports 5 volt tolerant i/o (except appi). low power 2.5 volt 0.25 m cmos technology.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 3 329 pin plastic ball grid array (pbga) package.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 4 2 applications ietf ppp interfaces for routers tdm switches frame relay interfaces for atm or frame relay switches and multiplexors funi or frame relay service inter-working interfaces for atm switches and multiplexors. internet/intranet access equipment. packet-based dslam equipment. packet over sonet.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 5 3 references 1. international organization for standardization, iso standard 3309-1993, "information technology - telecommunications and information exchange between systems - high-level data link control (hdlc) procedures - frame structure", december 1993. 2. rfc-1662 ? ?ppp in hdlc-like framing" internet engineering task force, july 1994. 3. go-mvip, ?mvip-90 standard?, october 1994, release 1.1. 4. go-mvip, ?h-mvip standard?, january 1997, release 1.1a.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 6 4 block diagram r e c e i v e c h a n n e l a s s i g n e r ( r c a s 6 7 2 ) t r a n s m i t c h a n n e l a s s i g n e r ( t c a s 6 7 2 ) r e c e i v e h d l c p r o c e s s o r / p a r t i a l p a c k e t b u f f e r ( r h d l 6 7 2 ) t r a n s m i t h d l c p r o c e s s o r / p a r t i a l p a c k e t b u f f e r ( t h d l 6 7 2 ) p e r f o r m a n c e m o n i t o r ( p m o n ) r e c e i v e a n y - p h y p a c k e t i n t e r f a c e ( r a p i 6 7 2 ) tbclk tbd pmctest tdo tdi tck tms trstb rbclk rbd rstb j t a g p o r t r x c l k r x a d d r [ 2 : 0 ] r p a r e n b r x d a t a [ 1 5 : 0 ] r x p r t y r s x r e o p r m o d r e r r r v a l t r a n s m i t a n y - p h y p a c k e t i n t e r f a c e ( t a p i 6 7 2 ) t x c l k t x a d d r [ 1 2 : 0 ] t p a 1 [ 2 : 0 ] t p a 2 [ 2 : 0 ] t r d y t x d a t a [ 1 5 : 0 ] t x p r t y t s x t e o p t m o d t e r r m i c r o p r o c e s s o r i n t e r f a c e in tb rdb wrb csb ale a[11:2] d[15:0] sysclk r d [ 3 1 : 0 ] r c l k [ 3 1 : 0 ] r f p b [ 3 : 0 ] r m v c k [ 3 : 0 ] r m v 8 d c r m v 8 f p c r f p 8 b t d [ 3 1 : 0 ] t c l k [ 3 1 : 0 ] t f p b [ 3 : 0 ] t m v c k [ 3 : 0 ] t m v 8 d c t m v 8 f p c t f p 8 b
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 7 5 description the pm7381 freedm-32a672 frame engine and datalink manager device is a monolithic integrated circuit that implements hdlc processing for a maximum of 672 bi-directional channels. the freedm-32a672 may be configured to support h-mvip, channelised t1/j1/e1 or unchannelised traffic across 32 physical links. the freedm-32a672 may be configured to interface with h-mvip digital telephony buses at 2.048 mbps. for 2.048 mbps h-mvip links, the freedm- 32a672 allows up to 672 bi-directional hdlc channels to be assigned to individual time-slots within a maximum of 32 h-mvip links. the channel assignment supports the concatenation of time-slots (n x ds0) up to a maximum of 32 concatenated time-slots for each 2.048 mbps h-mvip link. time-slots assigned to any particular channel need not be contiguous within the h-mvip link. when configured for 2.048 mbps h-mvip operation, the freedm-32a672 partitions the 32 physical links into 4 logical groups of 8 links. links 0 through 7, 8 through 15, 16 through 23 and 24 through 31 make up the 4 logical groups. links in each logical group share a common clock and a common type 0 frame pulse in each direction. the freedm-32a672 may be configured to interface with h-mvip digital telephony buses at 8.192 mbps. for 8.192 mbps h-mvip links, the freedm- 32a672 allows up to 672 bi-directional hdlc channels to be assigned to individual time-slots within a maximum of 8 h-mvip links. the channel assignment supports the concatenation of time-slots (n x ds0) up to a maximum of 128 concatenated time-slots for each 8.192 h-mvip link. time-slots assigned to any particular channel need not be contiguous within the h-mvip link. when configured for 8.192 mbps h-mvip operation, the freedm-32a672 partitions the 32 physical links into 8 logical groups of 4 links. only the first link, which must be located at physical links numbered 4m (0 m 7), of each logical group can be configured for 8.192 mbps operation. the remaining 3 physical links in the logical group (numbered 4m+1, 4m+2 and 4m+3) are unused. all links configured for 8.192 mbps h-mvip operat ion will share a common type 0 frame pulse, a common frame pulse clock and a common data clock. for channelised t1/j1/e1 links, the freedm-32a672 allows up to 672 bi- directional hdlc channels to be assigned to individual time-slots within a maximum of 32 independently timed t1/j1 or e1 links. the gapped clock method to determine time-slot positions as per the freedm-8 and freedm-32 devices is retained. the channel assignment supports the concatenation of time- slots (n x ds0) up to a maximum of 24 concatenated time-slots for a t1/j1 link
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 8 and 31 concatenated time-slots for an e1 link. time-slots assigned to any particular channel need not be contiguous within the t1/j1 or e1 link. for unchannelised links, the freedm-32a672 processes up to 32 bi-directional hdlc channels within 32 independently timed links. the links can be of arbitrary frame format. when limited to three unchannelised links, each link can be rated at up to 51.84 mhz provided sysclk is running at 45 mhz. for lower rate unchannelised links, the freedm-32a672 processes up to 32 links each rated at up to 10 mhz. in this case, the aggregate clock rate of all the links is limited to 64 mhz. the freedm-32a672 supports mixing of up to 32 channelised t1/j1/e1, unchannelised and h-mvip links. the total number of channels in each direction is limited to 672. the aggregate instantaneous clock rate over all 32 possible links is limited to 64 mhz. the freedm-32a672 provides a low latency ?any-phy? packet interface (appi) to allow an external controller direct access into the 32 kbyte partial packet buffers. up to seven freedm-32a672 devices may share a single appi. for each of the transmit and receive appi, the external controller is the master of each freedm-32a672 device sharing the appi from the point of view of device selection. the external controller is also the master for channel selection in the transmit direction. in the receive direction, however, each freedm-32a672 device retains control over selection of its respective channels. the transmit and receive appi is made up of three groups of functional signals ? polling, selection and data transfer. the polling signals ar e used by the external controller to interrogate the status of the transmit and receive 32 kbyte partial packet buffers. the selection signals are used by the external controller to select a freedm- 32a672 device, or a channel within a freedm-32a672 device, for data transfer. the data transfer signals provide a means of transferring data across the appi between the external controller and a freedm-32a672 device. in the receive direction, polling and selection are done at the device level. polling is not decoupled from selection, as the receive address pins serve as both a device poll address and to select a freedm-32a672 device. in response to a positive poll, the external controller may select that freedm-32a672 device for data transfer. once selected, the freedm-32a672 prepends an in-band channel address to each partial packet transfer across the receive appi to associate the data with a channel. a freedm-32a672 must not be selected after a negative poll response. in the transmit direction, polling is done at the channel level. polling is completely decoupled from selection. to increase the polling bandwidth, up to two channels may be polled simultaneously. the polling engine in the external
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 9 controller runs independently of other activity on the transmit appi. in response to a positive poll, the external controller may commence partial packet data transfer across the transmit appi for the successfully polled channel of a freedm-32a672 device. the external controller must prepend an in-band channel address to each partial packet transfer across the transmit appi to associate the data with a channel. in the receive direction, the freedm-32a672 performs channel assignment and packet extraction and validation. for each provisioned hdlc channel, the freedm-32a672 delineates the packet boundaries using flag sequence detection, and performs bit de-stuffing. sharing of opening and closing flags, as well as sharing of zeros between flags are supported. the resulting packet data is placed into the internal 32 kbyte partial packet buffer ram. the partial packet buffer acts as a logical fifo for each of the assigned channels. an external controller transfers partial packets out of the ram, across the receive appi bus, into host packet memory. the freedm-32a672 validates the frame check sequence for each packet, and verifies that the packet is an integral number of octets in length and is within a programmable minimum and maximum lengths. receive appi bus latency may cause one or more channels to overflow, in which case, the packets are aborted. the freedm-32a672 reports the status of each packet on the receive appi at the end of each packet transfer. alternatively, in the receive direction, the freedm-32a672 supports a transparent operating mode. for each provisioned transparent channel, the freedm-32a672 directly transfers the received octets onto the receive appi verbatim. if the transparent channel is assigned to a channelised link, then the octets are aligned to the received time-slots. in the transmit direction, an external controller provides packets to transmit using the transmit appi. for each provisioned hdlc channel, an external controller transfers partial packets, across the transmit appi, into the internal 32 kbyte transmit partial packet buffer. the partial packets are read out of the partial packet buffer by the freedm-32a672 and a frame check sequence is optionally calculated and inserted at the end of each packet. bit stuffing is performed before being assigned to a particular link. the flag or idle sequence is automatically inserted when there is no packet data for a particular channel. sequential packets are optionally separated by a single flag (combined opening and closing flag) or up to 128 flags. zeros between flags are not shared in the transmit direction although, as stated previously, they are accepted in the receive direction. transmit appi bus latenc y may cause one or more channels to underflow, in which case, the packets are aborted. the freedm-32a672 generates an interrupt to notify the host of aborted packets. for normal traffic, an abort sequence is generated, followed by inte r-frame time fill characters (flags or
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 10 all-ones bytes) until a new packet is sourced on the transmit appi. the freedm-32a672 will not attempt to re-transmit aborted packets. alternatively, in the transmit direction, the freedm-32a672 supports a transparent operating mode. for each provisioned transparent channel, the freedm-32a672 directly inserts the transmitted octets provided on the transmit appi. if the transparent channel is assigned to a channelised link, then the octets are aligned to the transmitted time-slots. if a channel underflows due to excessive transmit appi bus latency, an abort sequence is generated, followed by inter-frame time fill characters (flags or all-ones bytes) to i ndicate idle channel. data resumes immediately when the freedm-32a672 receives new data on the transmit appi. the freedm-32a672 is configured, controlled and monitored using the microprocessor interface. the freedm-32a672 is implemented in low power 2.5 volt 0.25 m cmos technology. all freedm-32a672 i/o except those belonging to the appi are 5 volt tolerant. the appi i/o are 3.3 volt tolerant. the freedm-32a672 is packaged in a 329 pin plastic ball grid array (pbga) package.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 11 6 pin diagram the freedm-32a672 is manufactured in a 329 pin plastic ball grid array package. 2322212019181716151413121110987654321 a rmvck[2] rd[16] rclk[17] rclk[19] rd[21] rd[22] rd[23] rd[24] rclk[25] rclk[27] rclk[29] vdd2v5 rdb a[10] a[6] a[3] d[13] d[11] d[9] d[6] d[2] d[0] t pa2[2] a b rfpb[2] rclk[16] rd[18] rd[20] vdd2v5 rclk[22] rfpb[3] rclk[24] rclk[26] rd[28] rd[30] rclk[31] intb a[11] a[8] a[4] d[15] d[12] vdd2v5 d[7] d[3] tp a2[0] tpa2[1] b c rd[15] rstb rclk[15] rclk[18] rclk[20] rclk[21] rmvck[3] rd[25] rd[27] rclk[28] rclk[30] rd[31] csb ale a[9] a[5] a[2] d[10] d[8] d[4] d[1] n.c. tpa1 [1] c d rclk[13] rd[13] rclk[14] rd[17] rd[19] vdd3v3 rclk[23] vss rd[26] vdd3v3 rd[29] vss wrb vdd3v3 a[7] vss d[14] vdd3v3 d[5] tpa1[2] tpa1[0] txaddr [10] txaddr [11] d e rd[12] vdd2v5 rclk[12] rd[14] txaddr [12] txaddr [9] vdd2v5 txaddr [8] e f rd[11] rclk[10] rclk[11] vss vss txaddr [7] txaddr [5] txaddr [6] f g rd[10] rd[9] rclk[8] rclk[9] bottom view txaddr [3] txaddr [1] txaddr [2] txaddr [4] g h rd[8] rmvck[1] rfpb[1] vdd3v3 vdd3v3 txdata [15] txclk txaddr [0] h j rclk[7] rclk[6] rd[6] rd[7] txdata [13] txdata [11] txdata [12] txdata [14] j k sysclk rclk[5] rd[5] vss vss vss vss vss vss vss txdata [8] txdata [9] txdata [10] k l rd[4] rd[3] rclk[3] rclk[4] vss vss vss vss vss txprty txdata [6] txdata [7] tsx l m vdd2v5 rclk[2] rd[2] vdd3v3 vss vss vss vss vss vdd3v3 txdata [5] txdata [4] vdd2v5 m n rclk[0] rd[1] rclk[1] rd[0] vss vss vss vss vss txdata [0] txdata [2] txdata [3] txdata [1] n p rmv8fpc rfpb[0] rmvck[0] vss vss vss vss vss vss vss teop tmod terr p r rbd rmv8dc rfp8b rbclk rpa trdy rval renb r t tck tms trstb vdd3v3 vdd3v3 reop rmod rerr t u tfp8b tdo tdi tmv8dc rxdata [14] rxprty rxdata [15] rxdata [13] u v tfpb[0] tmv8fpc tmvck[0] vss vss rxdata [10] rxdata [12] rxdata [11] v w td[0] vdd2v5 tclk[0] td[2] rxdata [6] rxdata [8] vdd2v5 rxdata [9] w y tclk[1] td[1] tclk[2] td[4] tmvck[1] vdd3v3 td[12] vss tclk[15] vdd3v3 tclk[17] vss td[22] vdd3v3 td[24] vss tclk[27] vdd3v3 tbd rxaddr [1] rxdata [5] rsx rxdata [7] y aa tclk[3] td[3] tclk[6] tfpb[1] td[9] td[10] td[13] tclk[14] tmvck[2] td[17] tclk[18] td[20] tclk[20] tclk[22] tfpb[3] td[25] tclk[26] tclk[29] tcl k[30] tbclk rxdata [2] rxdata [4] rxdata [3] aa ab td[5] tclk[4] tclk[7] tclk[8] vdd2v5 td[11] tclk[12] td[14] tfpb[2] tclk[16] td[19] tclk[19] td[21] td[23] tmvck[3] tclk[25] td[27] tclk[28] vdd2 v5 td[31] pmctest rxaddr [2] rxdata [1] ab ac tclk[5] td[6] td[7] td[8] tclk[9] tclk[10] tclk[11] tclk[13] td[15] td[16] td[18] vdd2v5 tclk[21] tclk[23] tclk[24] td[26] td[28] td[29] td[30] tc lk[31] rxaddr [0] rxclk rxdata [0] ac 2322212019181716151413121110987654321
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 12 7 pin description table 1 ? line side interface signals (154) pin name type pin no. function rclk[0] rclk[1] rclk[2] rclk[3] rclk[4] rclk[5] rclk[6] rclk[7] rclk[8] rclk[9] rclk[10] rclk[11] rclk[12] rclk[13] rclk[14] rclk[15] rclk[16] rclk[17] rclk[18] rclk[19] rclk[20] rclk[21] rclk[22] rclk[23] rclk[24] rclk[25] rclk[26] rclk[27] rclk[28] rclk[29] rclk[30] rclk[31] input n23 n21 m22 l21 l20 k22 j22 j23 g21 g20 f22 f21 e21 d23 d21 c21 b22 a21 c20 a20 c19 c18 b18 d17 b16 a15 b15 a14 c14 a13 c13 b12 the receive line clock signals (rclk[31:0]) contain the recovered line clock for the 32 independently timed links. processing of the receive links are on a priority basis, in descending order from rclk[0] to rclk[31]. therefore, the highest rate link should be connected to rclk[0] and the lowest to rclk[31]. for channelised t1/j1 or e1 links, rclk[n] must be gapped during the framing bit (for t1/j1 interfaces) or during time-slot 0 (for e1 interfaces) of the rd[n] stream. the freedm-32a672 uses the gapping information to determine the time-slot alignment in the receive stream. rclk[31:0] is nominally a 50% duty cycle clock of frequency 1.544 mhz for t1/j1 links and 2.048 mhz for e1 links. for unchannelised links, rclk[n] must be externally gapped during the bits or time- slots that are not part of the transmission format payload (i.e. not part of the hdlc packet). rclk[2:0] is nominally a 50% duty cycle clock between 0 and 51.84 mhz. rclk[31:3] is nominally a 50% duty cycle clock between 0 and 10 mhz. the rclk[n] inputs are invalid and should be forced to a low state when their associated link is configured for operation in h-mvip mode.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 13 pin name type pin no. function rd[0] rd[1] rd[2] rd[3] rd[4] rd[5] rd[6] rd[7] rd[8] rd[9] rd[10] rd[11] rd[12] rd[13] rd[14] rd[15] rd[16] rd[17] rd[18] rd[19] rd[20] rd[21] rd[22] rd[23] rd[24] rd[25] rd[26] rd[27] rd[28] rd[29] rd[30] rd[31] input n20 n22 m21 l22 l23 k21 j21 j20 h23 g22 g23 f23 e23 d22 e20 c23 a22 d20 b21 d19 b20 a19 a18 a17 a16 c16 d15 c15 b14 d13 b13 c12 the receive data signals (rd[31:0]) contain the recovered line data for the 32 independently timed links in normal mode (pmctest set low). processing of the receive links is on a priority basis, in descending order from rd[0] to rd[31]. therefore, the highest rate link should be connected to rd[0] and the lowest to rd[31]. for h-mvip links, rd[n] contains 32/128 time-slots, depending on the h-mvip data rate configured (2.048 or 8.192 mbps). when configured for 2.048 mbps h-mvip operation, rd[31:24], rd[23:16], rd[15:8] and rd[7:0] are sampled on every 2 nd rising edge of rmvck[3], rmvck[2], rmvck[1] and rmvck[0] respectively (at the ? point of the bit interval). when configured for 8.192 mbps h-mvip operation, rd[4m] (0 m 7) are sampled on every 2 nd rising edge of rmv8dc (at the ? point of the bit interval). for channelised links, rd[n] contains the 24 (t1/j1) or 31 (e1) time-slots that comprise the channelised link. rclk[n] must be gapped during the t1/j1 framing bit position or the e1 frame alignment signal (time-slot 0). the freedm-32a672 uses the location of the gap to determine the channel alignment on rd[n]. rd[31:0] are sampled on the rising edge of the corresponding rclk[31:0]. for unchannelised links, rd[n] contains the hdlc packet data. for certain transmission formats, rd[n] may contain place holder bits or time-slots. rclk[n] must be externally gapped during the place holder positions in the rd[n] stream. the freedm-32a672 supports a maximum data rate of 10 mbit/s
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 14 pin name type pin no. function on an individual rd[31:3] link and a maximum data rate of 51.84 mbit/s on rd[2:0]. rd[31:0] are sampled on the rising edge of the corresponding rclk[31:0]. rmvck[0] rmvck[1] rmvck[2] rmvck[3] input p21 h22 a23 c17 the receive mvip data clock signals (rmvck[3:0]) provide the receive data clock for the 32 links when configured to operate in 2.048 mbps h-mvip mode. when configured for 2.048 mbps h-mvip operation, the 32 links are partitioned into 4 groups of 8, and each group of 8 links share a common data clock. rmvck[0], rmvck[1], rmvck[2] and rmvck[3] sample the data on links rd[7:0], rd[15:8], rd[23:16] and rd[31:24] respectively. each rmvck[n] is nominally a 50% duty cycle clock with a frequency of 4.096 mhz. rmvck[n] is ignored and should be tied low when no physical link within the associated logical group of 8 links is configured for operation in 2.048 mbps h-mvip mode. rfpb[0] rfpb[1] rfpb[2] rfpb[3] input p22 h21 b23 b17 the receive frame pulse signals (rfpb[3:0]) reference the beginning of each frame for the 32 links when configured for operation in 2.048 mbps h-mvip mode. when configured for 2.048 mbps h-mvip operation, the 32 links are partitioned into 4 groups of 8, and each group of 8 links share a common frame pulse. rfpb[0], rfpb[1], rfpb[2] and rfpb[3] reference the beginning of a frame on links rd[7:0], rd[15:8], rd[23:16] and rd[31:24] respectively. when configured for operation in 2.048 mbps h-mvip mode, rfpb[n] is sampled on the falling edge of rmvck[n]. otherwise, rfpb[n] is ignored and should be tied low.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 15 pin name type pin no. function rfp8b input r21 the receive frame pulse for 8.192 mbps h- mvip signal (rfp8b) references the beginning of each frame for links configured for operation in 8.192 mbps h-mvip mode. rfp8b references the beginning of a frame for any link configured for 8.192 mbps h- mvip operation. only links rd[4m] (0 m 7) may be configured for 8.192 mbps h-mvip operation. when one or more links are configured for 8.192 mbps h-mvip operation, rfp8b is sampled on the falling edge of rmv8fpc. when no links are configured for 8.192 mbps h-mvip operation, rfp8b is ignored and should be tied low. rmv8fpc input p23 the receive 8.192 mbps h-mvip frame pulse clock signal (rmv8fpc) provides the receive frame pulse clock for links configured for operation in 8.192 mbps h- mvip mode. rmv8fpc is used to sample rfp8b. rmv8fpc is nominally a 50% duty cycle, clock with a frequency of 4.096 mhz. the falling edge of rmv8fpc must be aligned with the falling edge of rmv8dc with no more than 10 ns skew. rmv8fpc is ignored and should be tied low when no physical links are configured for operation in 8.192 mbps h-mvip mode.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 16 pin name type pin no. function rmv8dc input r22 the receive 8.192 mbps h-mvip data clock signal (rmv8dc) provides the receive data clock for links configured to operate in 8.192 mbps h-mvip mode. rmv8dc is used to sample data on rd[4m] (0 m 7) when link 4m is configured for 8.192 mbps h-mvip operation. rmv8dc is nominally a 50% duty cycle clock with a frequency of 16.384 mhz. rmv8dc is ignored and should be tied low when no physical links are configured for operation in 8.192 mbps h-mvip mode. rbd tristate output r23 the receive bert data signal (rbd) contains the receive bit error rate test data. rbd reports the data on the selected one of the receive data signals (rd[31:0]) and is updated on the falling edge of rbclk. rbd may be tristated by setting the rben bit in the freedm-32a672 master bert control register low. bert is not supported for h-mvip links. rbclk tristate output r20 the receive bert clock signal (rbclk) contains the receive bit error rate test clock. rbclk is a buffered version of the selected one of the receive clock signals (rclk[31:0]). rbclk may be tristated by setting the rben bit in the freedm- 32a672 master bert control register low. bert is not supported for h-mvip links.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 17 pin name type pin no. function tclk[0] tclk[1] tclk[2] tclk[3] tclk[4] tclk[5] tclk[6] tclk[7] tclk[8] tclk[9] tclk[10] tclk[11] tclk[12] tclk[13] tclk[14] tclk[15] tclk[16] tclk[17] tclk[18] tclk[19] tclk[20] tclk[21] tclk[22] tclk[23] tclk[24] tclk[25] tclk[26] tclk[27] tclk[28] tclk[29] tclk[30] tclk[31] input w21 y23 y21 aa23 ab22 ac23 aa21 ab21 ab20 ac19 ac18 ac17 ab17 ac16 aa16 y15 ab14 y13 aa13 ab12 aa11 ac11 aa10 ac10 ac9 ab8 aa7 y7 ab6 aa6 aa5 ac4 the transmit line clock signals (tclk[31:0]) contain the transmit clocks for the 32 independently timed links. processing of the transmit links is on a priority basis, in descending order from tclk[0] to tclk[31]. therefore, the highest rate link should be connected to tclk[0] and the lowest to tclk[31]. for channelised t1/j1 or e1 links, tclk[n] must be gapped during the framing bit (for t1/j1 interfaces) or during time-slot 0 (for e1 interfaces) of the td[n] stream. the freedm-32a672 uses the gapping information to determine the time-slot alignment in the transmit stream. for unchannelised links, tclk[n] must be externally gapped during the bits or time- slots that are not part of the transmission format payload (i.e. not part of the hdlc packet). tclk[2:0] is nominally a 50% duty cycle clock between 0 and 51.84 mhz. tclk[31:3] is nominally a 50% duty cycle clock between 0 and 10 mhz. typical values for tclk[31:0] include 1.544 mhz (for t1/j1 links) and 2.048 mhz (for e1 links). the tclk[n] inputs are invalid and should be tied low when their associated link is configured for operation in h-mvip mode.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 18 pin name type pin no. function td[0] td[1] td[2] td[3] td[4] td[5] td[6] td[7] td[8] td[9] td[10] td[11] td[12] td[13] td[14] td[15] td[16] td[17] td[18] td[19] td[20] td[21] td[22] td[23] td[24] td[25] td[26] td[27] td[28] td[29] td[30] td[31] output w23 y22 w20 aa22 y20 ab23 ac22 ac21 ac20 aa19 aa18 ab18 y17 aa17 ab16 ac15 ac14 aa14 ac13 ab13 aa12 ab11 y11 ab10 y9 aa8 ac8 ab7 ac7 ac6 ac5 ab4 the transmit data signals (td[31:0]) contain the transmit data for the 32 independently timed links in normal mode (pmctest set low). processing of the transmit links is on a priority basis, in descending order from td[0] to td[31]. therefore, the highest rate link should be connected to td[0] and the lowest to td[31]. for h-mvip links, td[n] contain 32/128 time-slots, depending on the h-mvip data rate configured (2.048 or 8.192 mbps). when configured for 2.048 mbps h-mvip operation, td[31:24], td[23:16], td[15:8] and td[7:0] are updated on every 2 nd falling edge of tmvck[3], tmvck[2], tmvck[1] and tmvck[0] respectively. when configured for 8.192 mbps h-mvip operation, td[4m] (0 m 7) are updated on every 2 nd falling edge of tmv8dc. for channelised links, td[n] contains the 24 (t1/j1) or 31 (e1) time-slots that comprise the channelised link. tclk[n] must be gapped during the t1/j1 framing bit position or during the e1 frame alignment signal (time-slot 0). the freedm-32a672 uses the location of the gap to determine the channel alignment on td[n]. td[31:0] are updated on the fallin g edge of the corresponding tclk[31:0]. for unchannelised links, td[n] contains the hdlc packet data. for certain transmission formats, td[n] may contain place holder bits or time-slots. tclk[n] must be externally gapped during the place holder positions in the td[n] stream. the freedm-32a672 supports a maximum data rate of 10 mbit/s on an individual td[31:3] link and a maximum data rate of 51.84 mbit/s on td[2:0].
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 19 pin name type pin no. function td[31:0] are updat ed on the fallin g edge of the corresponding tclk[31:0] clock. tmvck[0] tmvck[1] tmvck[2] tmvck[3] input v21 y19 aa15 ab9 the transmit mvip data clock signals (tmvck[3:0]) provide the transmit data clocks for the 32 links when configured to operate in 2.048 mbps h-mvip mode. when configured for 2.048 mbps h-mvip operation, the 32 links are partitioned into 4 groups of 8, and each group of 8 links share a common clock. tmvck[0], tmvck[1], tmvck[2] and tmvck[3] update the data on links td[7:0], td[15:8], td[23:16] and td[31:24] respectively. each tmvck[n] is nominally a 50% duty cycle clock with a frequency of 4.096 mhz. tmvck[n] is unused and should be tied low when no physical links within the associated group of 8 logical links is configured for operation in 2.048 mbps h-mvip mode. tfpb[0] tfpb[1] tfpb[2] tfpb[3] input v23 aa20 ab15 aa9 the transmit frame pulse signals (tfpb[3:0]) reference the beginning of each frame when configured for operation in 2.048 mbps h-mvip mode. when configured for 2.048 mbps h-mvip operation, the 32 links are partitioned into 4 groups of 8, and each group of 8 links share a common frame pulse. tfpb[0], tfpb[1], tfpb[2] and tfpb[3] reference the beginning of a frame on links td[7:0], td[15:8], td[23:16] and td[31:24] respectively. when configured for operation in 2.048 mbps h-mvip mode, tfpb[n] is sampled on the falling edge of tmvck[n]. otherwise, tfpb[n] is ignored and should be tied low.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 20 pin name type pin no. function tfp8b input u23 the transmit frame pulse for 8.192 mbps h- mvip signal (tfp8b) references the beginning of each frame for links configured to operate in 8.192 mbps h-mvip mode. tfp8b references the beginning of a frame for any link configured for 8.192 mbps h- mvip operation. only links 4m (0 m 7) may be configured for 8.192 mbps h-mvip operation. when one or more links are configured for 8.192 mbps h-mvip operation, tfp8b is sampled on the falling edge of tmv8fpc. when no links are configured for 8.192 mbps h-mvip operation, tfpb[n] is ignored and should be tied low. tmv8fpc input v22 the transmit 8.192 mbps h-mvip frame pulse clock signal (tmv8fpc) provides the transmit frame pulse clock for links configured for operation in 8.192 mbps h- mvip mode. tmv8fpc is used to sample tfp8b. tmv8fpc is nominally a 50% duty cycle, clock with a frequency of 4.096 mhz. the falling edge of tmv8fpc must be aligned with the falling edge of tmv8dc with no more than 10 ns skew. tmv8fpc[n] is ignored and should be tied low when no physical links are configured for operation in 8.192 mbps h-mvip mode.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 21 pin name type pin no. function tmv8dc input u20 the transmit 8.192 mbps h-mvip data clock signal (tmv8dc) provides the transmit data clock for links configured to operate in 8.192 mbps h-mvip mode. tmv8dc is used to update data on td[4m] (0 m 7) when link 4m is configured for 8.192 mbps h-mvip operation. tmv8dc is nominally a 50% duty cycle clock with a frequency of 16.384 mhz. tmv8dc is unused and should be tied low when no physical links are configured for operation in 8.192 mbps h-mvip mode. tbd input y5 the transmit bert data signal (tbd) contains the transmit bit error rate test data. when the tberten bit in the bert control register is set high, the data on tbd is transmitted on the selected one of the transmit data signals (td[31:0]). tbd is sampled on the rising edge of tbclk. bert is not supported for h-mvip links. tbclk tristate output aa4 the transmit bert clock signal (tbclk) contains the transmit bit error rate test clock. tbclk is a buffered version of the selected one of the transmit clock signals (tclk[31:0]). tbclk may be tristated by setting the tben bit in the freedm- 32a672 master bert control register low. bert is not supported for h-mvip links.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 22 table 2 ? any-phy packet interface signals (70) pin name type pin no. function txclk input h2 the transmit clock signal (txclk) provides timing for the trans mit any-phy packet interface. txclk is a nominally 50% duty cycle, 25 to 50 mhz clock. txaddr[0] txaddr[1] txaddr[2] txaddr[3] txaddr[4] txaddr[5] txaddr[6] txaddr[7] txaddr[8] txaddr[9] txaddr[10] txaddr[11] txaddr[12] input h1 g3 g2 g4 g1 f2 f1 f3 e1 e3 d2 d1 e4 the transmit address signals (txaddr[12:0]) provide a channel address for polling a transmit channel fifo. the 10 least significant bits provide the channel number (0 to 671) while the 3 most significant bits select one of seven possible freedm-32a672 devices sharing a single external controller. (one address is reserved as a null address.) the tx appi of each freedm-32a672 device is identified by the base address in the tapi672 control register. the txaddr[12:0] signals are sampled on the rising edge of txclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 23 pin name type pin no. function tpa1[0] tpa1[1] tpa1[2] tpa2[0] tpa2[1] tpa2[2] tristate output d3 c1 d4 b2 b1 a1 the transmit packet available signals (tpa1[2:0] and tpa2[2:0]) reflects the status of a poll of two transmit channel fifos. tpa1[2:0] returns the polled results for channel address ?n? provided on txaddr[12:0] and tpa2[2:0] returns the polled results for channel address ?n+1?. tpan[2] reports packet underrun events and tpan[1:0] report the fill state of the transmit channel fifo. tpan[2] is set high when one or more packets has underrun on the channel and a further data transfer has occurred since it was last polled. when tpan[2] is set low, no packet has underrun on the channel since the last poll. tpan[1:0] are coded as follows: tpan[1:0] = ?11? => starving tpan[1:0] = ?10? => (reserved) tpan[1:0] = ?01? => space tpan[1:0] = ?00? => full a ?starving? polled response indicates that the polled transmit channel fifo is at risk of underflowing and should be supplied with data as soon as possible. a ?space? polled response indicates that the polled transmit channel fifo can accept xfer[3:0] pl us one blocks (16 bytes per block) of data. a ?full? polled response indicates that the polled transmit channel fifo cannot accept xfer[3:0] plus one blocks of data. (xfer[3:0] is a per-channel programmable value ? see description of register 0x38c.) it is the responsibility of the external controller to prevent channel underflow conditions by adequately polling each channel before data transfer. tpan[2:0] are tristate during reset and when a device address other than the freedm- 32a672?s base address is provided on txaddr[12:10].
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 24 pin name type pin no. function tpan[2:0] are updated on the rising edge of txclk. trdy tristate output r3 the transmit ready signal (trdy) indicates the ability of the transmit any-phy packet interface (appi) to accept data. when trdy is set low, the transmit appi is unable to accept further data. when trdy is set high, data provided on the transmit appi will be accepted by the freedm-32a672 device. trdy is asserted one txclk cycle after tsx is sampled high. trdy is asserted by the freedm-32a672 device which was selected by the in-band channel address on txdata[15:0] when tsx was sampled high. if trdy is driven low, the external controller must hold the data on txdata[15:0] until trdy is driven high. trdy may be driven low for 0 or more txclk cycles before it is driven high. trdy is always driven tristate the txclk cycle after it is driven high. trdy is tristate during reset. trdy is updated on the rising edge of txclk. it is recommended that trdy be connected externally to a weak pull-up, e.g. 10 k .
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 25 pin name type pin no. function txdata[0] txdata[1] txdata[2] txdata[3] txdata[4] txdata[5] txdata[6] txdata[7] txdata[8] txdata[9] txdata[10] txdata[11] txdata[12] txdata[13] txdata[14] txdata[15] input n4 n1 n3 n2 m2 m3 l3 l2 k3 k2 k1 j3 j2 j4 j1 h3 the transmit data signals (txdata[15:0]) contain the transmit any-phy packet interface (appi) data provided by the external controller. data must be presented in big endian order, i.e. the byte in txdata[15:8] is transmitted by the freedm-32a672 before the byte in txdata[7:0]. the first word of each data transfer contains an address to identify the device and channel associated with the data being transferred. this prepended address must be qualified with the tsx signal. the 10 least significant bits provide the channel number (0 to 671) while the 3 most significant bits select one of seven possible freedm-32a672 devices sharing a single external controller. (one address is reserved as a null address.) the freedm-32a672 will not respond to channel addresses outside the range 0 to 671, nor to device addresses other than the base address stored in the tapi672 control register. the second and any subsequent words of each data transfer contain packet data. the txdata[15:0] signals are sampled on the rising edge of txclk. txprty input l4 the transmit parity signal (txprty) reflects the odd parity calculated over the txdata[15:0] signals. txprty is only valid when txdata[15:0] are valid. txprty is sampled on the rising edge of txclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 26 pin name type pin no. function tsx input l1 the transmit start of transfer signal (tsx) denotes the start of data transfer on the transmit appi. when the tsx signal is sampled high, the sampled word on the txdata[15:0] signals contain the device and channel address associated with the data to follow. when the tsx signal is sampled low, the sampled word on the txdata[15:0] signals do not contain a device/channel address. the tsx signal is sampled on the rising edge of txclk. teop input p3 the transmit end of packet signal (teop) denotes the end of a packet. teop is only valid during data transfer. when teop is sampled high, the data on txdata[15:0] is the last word of a packet. when teop is sampled low, the data on txdata[15:0] is not the last word of a packet. teop is sampled on the rising edge of txclk. tmod input p2 the transmit word modulo signal (tmod) indicates the size of the current word on txdata[15:0]. tmod is only valid when teop is sampled high. when tmod is sampled high and teop is sampled high, only the txdata[15:8] signals contain valid data and the txdata[7:0] signals are invalid. when tmod is sampled low and teop is sampled high, the complete word on txdata[15:0] contains valid data. tmod must be set low when teop is set low. tmod is sampled on the rising edge of txclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 27 pin name type pin no. function terr input p1 the transmit error signal (terr) indicates that the current packet is errored and should be aborted. terr is only valid when teop is sampled high. when terr is sampled high and teop is sampled high, the current packet is errored and the freedm-32a672 will respond accordingly. when terr is sampled low and teop is sampled high, the current packet is not errored. terr must be set low when teop is set low. terr is sampled on the rising edge of txclk. rxclk input ac2 the receive clock signal (rxclk) provides timing for the receive any-phy packet interface (appi). rxclk is a nominally 50% duty cycle, 25 to 50 mhz clock. rxaddr[0] rxaddr[1] rxaddr[2] input ac3 y4 ab2 the receive address signals (rxaddr[2:0]) serve two functions ? device polling and device selection. when polling, the rxaddr[2:0] signals provide an address for polling a freedm-32a672 device for receive data available in any one of its 672 channels. polling results are returned on the rpa tristate output. during selection, the address on the rxaddr[2:0] signals is qualified with the renb signal to select a freedm-32a672 device enabling it to output data on the receive appi. note that up to seven freedm-32a672 devices may share a single external controller (one address is reserved as a null address). the rx appi of each freedm-32a672 device is identified by the base address in the rapi672 control register. the rxaddr[2:0] signals are sampled on the rising edge of rxclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 28 pin name type pin no. function rpa tristate output r4 the receive packet available signal (rpa) reflects the status of a poll on the receive appi of a freedm-32a672 device. when rpa is set high, the polled freedm-32a672 device has xfer[3:0] plus one blocks (16 bytes per block) of data to transfer, or alternatively, a smaller amount of data which includes an end of packet. when rpa is set low, the polled freedm- 32a672 device does not have data ready to transfer. (xfer[3:0] is a per-channel programmable value ? see description of register 0x208.) a freedm-32a672 device must not be selected for receive data transfer unless it has been polled and responded that it has data ready to transfer. when the rxaddr[2:0] inputs match the base address in the rapi672 control register, that freedm-32a672 device drives rpa one rxclk cycle after sampling rxaddr[2:0]. rpa is tristate during reset and when a device address other than the freedm-32a672?s base address is provided on rxaddr[2:0]. rpa is updated on the rising edge of rxclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 29 pin name type pin no. function renb input r1 the receive enable signal (renb) qualifies the rxaddr[2:0] signals for selection of a freedm-32a672 device. when renb is sampled high and then low in consecutive rxclk cycles, the address on rxaddr[2:0] during the cycle when renb is sampled high selects a freedm-32a672 device enabling it to output data on the receive appi. the rx appi of each freedm-32a672 device is identified by the base address in the rapi672 control register. the polling function of the rxaddr[2:0] and rpa signals operates regardless of the state of renb. renb may also be used to throttle the freedm-32a672 during data transfer on the rx appi. when the freedm-32a672 samples renb high during data transfer, the freedm- 32a672 will pause the data transfer and tri-state the receive appi outputs (except rpa) until renb is returned low. since the any-phy bus specification does not support deselection during data transfers, the address on the rxaddr[2:0] inputs during the cycle before renb is returned low must either re-select the same freedm-32a672 device or be a null address. to commence data transfer, renb must be sampled low following device selection. it is the responsibility of the external controller to prevent overflow by providing each freedm- 32a672 device on an any-phy point to multi- point bus sufficient bandwidth through selection. renb is sampled on the rising edge of rxclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 30 pin name type pin no. function rxdata[0] rxdata[1] rxdata[2] rxdata[3] rxdata[4] rxdata[5] rxdata[6] rxdata[7] rxdata[8] rxdata[9] rxdata[10] rxdata[11] rxdata[12] rxdata[13] rxdata[14] rxdata[15] tristate output ac1 ab1 aa3 aa1 aa2 y3 w4 y1 w3 w1 v3 v1 v2 u1 u4 u2 the receive data signals (rxdata[15:0]) contain the receive any-phy packet interface (appi) data output by the freedm-32a672 when selected. data is presented in big endian format, i.e. the byte in rxdata[15:8] was received by the freedm-32a672 before the byte in rxdata[7:0]. the first word of each data transfer (when rsx is high) contains an address to identify the device and channel associated with the data being transferred. the 10 least significant bits (rxdata[9:0]) contain the channel number (0 to 671) and the 3 most significant bits (rxdata[15:13]) contain the device base address. the second and any subsequent words of each data transfer contain valid data. the freedm-32a672 may be programmed to overwrite rxdata[7:0] of the final word of each packet transfer (reop is high) with the status of packet reception when that packet is errored (rerr is high). this status information is bit mapped as follows: rxdata[0]=?1? => channel fifo overrun. rxdata[1]=?1? => max. packet length violation. rxdata[2]=?1? => fcs error. rxdata[3]=?1? => non-octet aligned. rxdata[4]=?1? => hdlc packet abort. rxdata[7:5]=?xh? => reserved. the rxdata[15:0] signals are tristate when the freedm-32a672 device is not selected via the renb signal. the rxdata[15:0] signals are updated on the rising edge of rxclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 31 pin name type pin no. function rxprty tristate output u3 the receive parity signal (rxprty) reflects the odd parity calculated over the rxdata[15:0] signals. rxprty is driven/tristate at the same time as rxdata[15:0]. rxprty is updated on the rising edge of rxclk. rsx tristate output y2 the receive start of transfer signal (rsx) denotes the start of data transfer on the receive appi. when the rsx signal is set high, the 3 most significant bits on the rxdata[15:0] signals contain the freedm-32a672 device address and the 10 least significant bits on the rxdata[15:0] signals contain the channel address associated with the data to follow. valid device addresses are in the range 0 through 7 (with one address reserved as a null address) and valid channel addresses are in the range 0 through 671. when the rsx signal is sampled low, the word on the rxdata[15:0] signals does not contain a device and channel address. rsx is tristate when the freedm-32a672 device is not selected via the renb signal. rsx is updated on the rising edge of rxclk. it is recommended that rsx be connected externally to a weak pull-down, e.g. 10 k . reop tristate output t3 the receive end of packet signal (reop) denotes the end of a packet. reop is only valid during data transfer. when reop is set high, rxdata[15:0] contains the last data byte of a packet. when reop is set low, rxdata[15:0] does not contain the last data byte of a packet. reop is tristate when the freedm-32a672 device is not selected via the renb signal. reop is updated on the rising edge of rxclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 32 pin name type pin no. function rmod tristate output t2 the receive word modulo signal (rmod) indicates the size of the current word on rxdata[15:0]. when rdat[15:0] does not contain the last byte of a packet (reop set low), rmod is set low. when rmod is set high and reop is set high, rxdata[15:8] contains the last data byte of a packet. when rmod is set low and reop is set high, rxdata[7:0] contains the last byte of the packet, or optionally, the error status byte. the behavior of rmod relates only to packet data and is unaffected when the freedm-32a672 device is programmed to overwrite rxdata[7:0] with status information when errored packets are received. rmod is tristate when the freedm-32a672 device is not selected via the renb signal. rmod is updated on the rising edge of rxclk. rerr tristate output t1 the receive error signal (rerr) indicates that the current packet is errored and should be discarded. when rdat[15:0] does not contain the last byte of a packet (reop set low), rerr is set low. when rerr is set high and reop is set high, the current packet is errored. when rerr is set low and reop is set high, the current packet is not errored. the freedm-32a672 may be programmed to overwrite rxdata[7:0] of the final word of each packet transfer (reop set high) with the status of packet reception when that packet is errored (rerr is high). rerr is tristated when the freedm-32a672 device is not selected via the renb signal. rerr is updated on the rising edge of rxclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 33 pin name type pin no. function rval tristate output r2 the receive data valid (rval) is asserted when packet data is being output on rxdata[15:0]. it is deasserted whenever the freedm-32a672 device is selected, but not outputting packet data on rxdata[15:0]. (e.g., when rsx is high and address/channel prepend is being output on rxdata[15:0], rval is deasserted.) rval is tristated when the freedm-32a672 device is not selected via the renb signal. rval is updated on the rising edge of rxclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 34 table 3 ? microprocessor interface signals (31) pin name type pin no. function d[0] d[1] d[2] d[3] d[4] d[5] d[6] d[7] d[8] d[9] d[10] d[11] d[12] d[13] d[14] d[15] i/o a2 c3 a3 b3 c4 d5 a4 b4 c5 a5 c6 a6 b6 a7 d7 b7 the bi-directional data signals (d[15:0]) provide a data bus to allow the freedm-32a672 device to interface to an external micro-processor. both read and write transactions are supported. the microprocessor interface is used to configure and monitor the freedm-32a672 device. a[2] a[3] a[4] a[5] a[6] a[7] a[8] a[9] a[10] a[11] input c7 a8 b8 c8 a9 d9 b9 c9 a10 b10 the address signals (a[11:2]) provide an address bus to allow the freedm-32a672 device to interface to an external micro- processor. all microprocessor accessible registers are dword aligned. ale input c10 the address latch enable signal (ale) latches the a[11:2] signals during the address phase of a bus transaction. when ale is set high, the address latches are transparent. when ale is set low, the address latches hold the address provided on a[11:2]. ale has an integral pull-up resistor.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 35 pin name type pin no. function wrb input d11 the write strobe signal (wrb) qualifies write accesses to the freedm-32a672 device. when csb is set low, the d[15:0] bus contents are clocked into the addressed register on the rising edge of wrb. rdb input a11 the read strobe signal (rdb) qualifies read accesses to the freedm-32a672 device. when csb is set low, the freedm-32a672 device drives the d[15:0] bus with the contents of the addressed register on the falling edge of rdb. csb input c11 the chip select signal (csb) qualifies read/write accesses to the freedm-32a672 device. the csb signal must be set low during read and write accesses. when csb is set high, the microprocessor interface signals are ignored by the freedm-32a672 device. if csb is not required (register accesses controlled only by wrb and rdb) then csb should be connected to an inverted version of the rstb signal. intb open- drain output b11 the interrupt signal (intb) indicates that an interrupt source is active and unmasked. when intb is set low, the freedm-32a672 device has an active interrupt that is unmasked. when intb is tristate, no interrupts are active, or an active interrupt is masked. please refer to the register description section of this document for possible interrupt sources and masking. it is the responsibility of the external microprocessor to read the status registers in the freedm-32a672 device to determine the exact cause of the interrupt. intb is an open drain output.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 36 table 4 ? miscellaneous interface signals (9) pin name type pin no. function sysclk input k23 the system clock (sysclk) provides timing for the core logic. sysclk is nominally a 50% duty cycle, 25 to 45 mhz clock. rstb input c22 the active low reset signal (rstb) signal provides an asynchronous freedm-32a672 reset. rstb is an asynchronous input. when rstb is set low, all freedm-32a672 registers are forced to their default states. in addition, td[31:0] are forced high and all appi output pins are forced tristate and will re main high or tristated, respectively, until rstb is set high. pmctest input ab3 the pmc production test enable signal (pmctest) places the freedm-32a672 is test mode. when pmctest is set high, production test vectors can be executed to verify manufacturing via the test mode interface signals ta[11:0], ta[12]/trs, trdb, twrb and tdat[15:0]. pmctest must be tied low for normal operation. tck input t23 the test clock signal (tck) provides timing for test operations that can be carried out using the ieee p1149.1 test access port. tms and tdi are sampled on the rising edge of tck. tdo is updated on the falling edge of tck. tms input t22 the test mode select signal (tms) controls the test operations that can be carried out using the ieee p1149.1 test access port. tms is sampled on the rising edge of tck. tms has an integral pull up resistor. tdi input u21 the test data input signal (tdi) carries test data into the freedm-32a672 via the ieee p1149.1 test access port. tdi is sampled on the rising edge of tck. tdi has an integral pull up resistor.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 37 pin name type pin no. function tdo tristate output u22 the test data output signal (tdo) carries test data out of the freedm-32a672 via the ieee p1149.1 test access port. tdo is updated on the falling edge of tck. tdo is a tristate output which is inactive except when scanning of data is in progress. trstb input t21 the active low test reset signal (trstb) provides an asynchronous freedm-32a672 test access port reset via the ieee p1149.1 test access port. trstb is an asynchronous input with an integral pull up resistor. note that when trstb is not being used, it must be connected to the rstb input. nc open c2 this pin must be left unconnected.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 38 table 5 ? production test interf ace signals (0 - multiplexed) pin name type pin no. function ta[0] ta[1] ta[2] ta[3] ta[4] ta[5] ta[6] ta[7] ta[8] ta[9] ta[10] ta[11] input g23 f23 e23 d22 e20 c23 a22 d20 b21 d19 b20 a19 the test mode address bus (ta[11:0]) selects specific registers during production test (pmctest set high) read and write accesses. ta[11:0] replace rd[21:10] when pmctest is set high. ta[12]/tr s input a16 the test register select signal (ta[12]/trs) selects between normal and test mode register accesses during production test (pmctest set high). trs is set high to select test registers and is set low to select normal registers. ta[12]/trs replaces rd[24] when pmctest is set high. trdb input a18 the test mode read enable signal (trdb) is set low during freedm-32a672 register read accesses during production test (pmctest set high). the freedm-32a672 drives the test data bus (tdat[15:0]) with the contents of the addressed register while trdb is low. trdb replaces rd[22] when pmctest is set high. twrb input a17 the test mode write enable signal (twrb) is set low during freedm-32a672 register write accesses during production test (pmctest set high). the contents of the test data bus (tdat[15:0]) are clocked into the addressed register on the rising edge of twrb. twrb replaces rd[23] when pmctest is set high.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 39 pin name type pin no. function tdat[0] tdat[1] tdat[2] tdat[3] tdat[4] tdat[5] tdat[6] tdat[7] tdat[8] tdat[9] tdat[10] tdat[11] tdat[12] tdat[13] tdat[14] tdat[15] i/o ac1 4 aa14 ac1 3 ab13 aa12 ab11 y11 ab10 y9 aa8 ac8 ab7 ac7 ac6 ac5 ab4 the bi-directional test mode data bus (tdat[15:0]) carries data read from or written to freedm-32a672 registers during production test. tdat[15:0] replace td[31:16] when pmctest is set high. table 6 ? power and ground signals (65) pin name type pin no. function vdd3v3[1] vdd3v3[2] vdd3v3[3] vdd3v3[4] vdd3v3[5] vdd3v3[6] vdd3v3[7] vdd3v3[8] vdd3v3[9] vdd3v3[10] vdd3v3[11] vdd3v3[12] vdd3v3[13] vdd3v3[14] power d6 d10 d14 d18 h4 h20 m4 m20 t4 t20 y6 y10 y14 y18 the vdd3v3[14:1] dc power pins should be connected to a well decoupled +3.3 v dc supply. these power pins provide dc current to the i/o pads.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 40 pin name type pin no. function vdd2v5[1] vdd2v5[2] vdd2v5[3] vdd2v5[4] vdd2v5[5] vdd2v5[6] vdd2v5[7] vdd2v5[8] vdd2v5[9] vdd2v5[10] vdd2v5[11] vdd2v5[12] power e2 m1 w2 ab5 ac1 2 ab19 w22 m23 e22 b19 a12 b5 the vdd2v5[12:1] dc power pins should be connected to a well decoupled +2.5 v dc supply. these power pins provide dc current to the digital core. vss[1] vss[2] vss[3] vss[4] vss[5] vss[6] vss[7] vss[8] vss[9] vss[10] vss[11] vss[12] vss[13] vss[14] ground d8 d12 d16 f4 f20 k4 k20 p4 p20 v4 v20 y8 y12 y16 the vss[14:1] dc ground pins should be connected to ground. they provide a ground reference for the 3.3 v rail. they also provide a ground reference for the 2.5 v rail.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 41 pin name type pin no. function vss[15] vss[16] vss[17] vss[18] vss[19] vss[20] vss[21] vss[22] vss[23] vss[24] vss[25] vss[26] vss[27] vss[28] vss[29] vss[30] vss[31] vss[32] vss[33] vss[34] vss[35] vss[36] vss[37] vss[38] vss[39] k10 k11 k12 k13 k14 l10 l11 l12 l13 l14 m10 m11 m12 m13 m14 n10 n11 n12 n13 n14 p10 p11 p12 p13 p14 the vss[39:15] dc ground pins should be connected to ground. they provide improved thermal properties for the 329 pbga package. notes on pin description: 1. all freedm-32a672 inputs and bi-directionals present minimum capacitive loading and, with the exception of the any-phy interface, are 5v tolerant. (the any-phy interface is 3.3v tolerant.) 2. all freedm-32a672 digital outputs and bi-directionals have 4 ma drive capability except the rbclk, tbclk, rbd, d[15:0] and intb outputs which have 8 ma drive capability and the any-phy outputs (tpan[2:0], trdy, rpa, rsx, reop, rxdata[15:0], rxprty, rmod and rerr) which also have 8 ma drive capability. 3. all freedm-32a672 outputs can be tristated under control of the ieee p1149.1 test access port, even those which do not tristate under normal operation. all outputs and bi-directionals with the exception of the any-phy
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 42 interface are 5 v tolerant when tristated. (the any-phy interface is 3.3v tolerant.) 4. all inputs with the exception of the any-phy and microprocessor interfaces are schmitt triggered. inputs ale, tms, tdi and trstb have internal pull- up resistors. 5. power to the vdd3v3 pins should be applied before power to the vdd2v5 pins is applied. similarly, power to the vdd2v5 pins should be removed before power to the vdd3v3 pins is removed.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 43 8 functional description 8.1 high speed multi-vendor in tegration protocol (h-mvip) h-mvip defines a synchronous, time division multiplexed (tdm) bus of nx64 kbps constant bit rate (cbr) data streams. each 64 kbps data stream (time- slot) carries an 8-bit byte of hdlc traffic, as described in the following section, and is characterised by 8 khz framing. h-mvip supports higher bandwidth applications on existing telephony networks by fitting more time-slots into a 125 s frame. the freedm-32a672 supports h-mvip data rates of 2.048 mbps and 8.192 mbps with 32 or 128 time-slots per frame and associated clocking frequencies of 4.096 and 16.384 mhz respectively. figure 1 shows a diagram of the h-mvip protocol supported by the freedm-32a672 device. figure 1 ? h-mvip protocol data clock (4, 16 mhz) frame pulse (8 khz) serial data b8 b1 b2 b8 ts 31/127 ts 0 ts 1 b1 ts 31/127 b2 b8 b7 125 us frame pulse clock (4 mhz) b7 8.2 high-level data link control (hdlc) protocol figure 2 shows a diagram of the synchronous hdlc protocol supported by the freedm-32a672 device. the incoming stream is examined for flag bytes (01111110 bit pattern) which deli neate the opening and closing of the hdlc packet. the packet is bit de-stuffed which discards a "0" bit which directly follows five contiguous "1" bits. the resulting hdlc packet size must be a multiple of an octet (8 bits) and within the expected minimum and maximum packet length limits. the minimum packet length is that of a packet containing two information bytes (address and control) and fcs bytes. for packets with crc-ccitt as fcs, the minimum packet length is four bytes while those with crc-32 as fcs,
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 44 the minimum length is six bytes. an hdlc packet is aborted when seven contiguous "1" bits (with no inserted "0" bits) are received. at least one flag byte must exist between hdlc packets for delineation. contiguous flag bytes, or all ones bytes between packets are used as an "int er-frame time fill". adjacent flag bytes may share zeros. figure 2 ? hdlc frame flag information fcs flag hdlc packet flag the crc algorithm for the frame checking sequence (fcs) field is either a crc-ccitt or crc-32 function. figure 3 shows a crc encoder block diagram using the generating polynomial g(x) = 1 + g 1 x + g 2 x 2 +?+ g n-1 x n-1 + x n . the crc-ccitt fcs is two bytes in size and has a generating polynomial g(x) = 1 + x 5 + x 12 + x 16 . the crc-32 fcs is four byte s in size and has a generating polynomial g(x) = 1 + x + x 2 + x 4 + x 5 + x 7 + x 8 + x 10 + x 11 + x 12 + x 16 + x 22 + x 23 + x 26 + x 32 . the first fcs bit received is the residue of the highest term. figure 3 ? crc generator d 0 d 1 g 1 d 2 d n-1 message parity check digits g 2 g n-1 lsb msb 8.3 receive channel assigner the receive channel assigner block (rcas672) processes up to 32 serial links. links may be configured to support 2.048 or 8.192 mbps h-mvip traffic, to support t1/j1/e1 channelised traffic or to support unchannelised traffic. when configured to support 2.048 mbps h-mvip traffic, each group of 8 links share a clock and frame pulse. all links configured for 8.192 mbps h-mvip traffic share a common clock and frame pulse. for t1/j1/e1 channelised traffic or for unchannelised traffic, each link is independent and has its own associated clock.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 45 for each link, the rcas672 performs a serial to parallel conversion to form data bytes. the data bytes are multiplexed, in byte serial format, for delivery to the receive hdlc processor / partial packet buffer block (rhdl672) at sysclk rate. in the event where multiple streams have accumulated a byte of data, multiplexing is performed on a fixed priority basis with link #0 having the highest priority and link #31 the lowest. from the point of view of the rcas672, links configured for h-mvip traffic behave identically to links configured for t1/j1/e1 channelised or unchannelised traffic in the back end, only differing on the link side as described herein. first, the number of time-slots in each frame is programmable to be 32 or 128 and has an associated data clock frequency that is double the data rate. this provides more bandwidth per link for applications requiring higher data densities on a single link. second, h-mvip links reference the start of each frame with a frame pulse, thereby avoiding having to gap the link clock during the framing bits/bytes of each frame. the frame pulse is provided by an h-mvip bus master and ensures that all agents sharing the h-mvip bus remain synchronized. when configured for operation in 2.048 mbps mode, the frame pulse is sampled using the same clock which samples the data. when configured for operation in 8.192 mbps h-mvip mode, the frame pulse is sampled using a separate frame pulse clock provided by an h-mvip bus master. the frame pulse clock has a synchronous timing relationship to the data clock. third, not all links are independent. when configured for operation in 2.048 mbps h-mvip mode, each group of 8 links share a clock and a frame pulse. links 0 through 7, 8 through 15, 16 through 23 and 24 through 31 each share a clock and a frame pulse. not all 8 links within each group need to be configured for operation in 2.048 mbps h-mvip mode. however, any link within each logical group of 8 which is configured for 2.048 mbps h-mvip operati on will share the same clock and frame pulse. when configured for operation in 8.192 mbps h-mvip mode, links 4m (0 m 7) share a frame pulse, a data clock and a frame pulse clock. again, not all eight 4m (0 m 7) links need to be configured for operation in 8.192 mbps h-mvip mode, however, any link which is configured for 8.192 mbps h-mvip operation will share the same frame pulse, data clock and frame pulse clock. if link 4m is configured for 8.192 mbps h-mvip operation, then data transferred on that link is ?spread? over links 4m, 4m+1, 4m+2 and 4m+3 from a channel assigner point of view. accordingly, when link 4m is configured for operation in 8.192 mbps h-mvip mode, links 4m+1, 4m+2 and 4m+3 must also be configured for operation in 8.192 mbps h-mvip mode. in the back end, the rcas672 extracts and processes the time-slots in the same way as channelised t1/j1/e1 traffic. links containing a t1/j1 or an e1 stream may be channelised. data at each time-slot may be independently assigned to a different channel. the rcas672 performs a table lookup to associate the link and time-slot identity with a channel.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 46 t1/j1 and e1 framing bits/bytes are identified by observing the gap in the link clock which is squelched during the framing bits/bytes. for unchannelised links, clock rates are limited to 51.84 mhz for links #0 to #2 and limited to 10 mhz for the remaining links. all data on each link belongs to one channel. for the case of a mixture of channelised, unchannelised and h-mvip links, the total instantaneous link rate over all the links is limited to 64 mhz. the rcas672 performs a table lookup using only the link number to determine the associated channel, as time-slots are non-existent in unchannelised links. the rcas672 provides diagnostic loopback that is selectable on a per channel basis. the rcas672 does not support diagnostic loopback for links configured as h-mvip. when a channel is in diagnostic loopback, stream data on the received links originally destined for that channel is ignored. transmit data of that channel is substituted in its place. 8.3.1 line interface translator (lit) the lit block translates the information on the 32 physical links into a suitable format for interpretation by the line interface block. the lit block performs three functions: data translation, clock translation and frame pulse generation. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode, the lit block translates the 128 time-slots on link 4m to the line interface block across links 4m, 4m+1, 4m+2 and 4m+3. the lit block provides time-slots 0 through 31, 32 through 63, 64 through 95 and 96 through 127 to the line interface block on links 4m, 4m+1, 4m+2 and 4m+3 respectively. when link 4m is configured for operation in 8.192 mbps h-mvip mode, data cannot be received on inputs rd[4m+3:4m+1]. however, links 4m+1, 4m+2 and 4m+3 must be programmed in the rcas672 link configuration register for 8.192 mbps h-mvip operation. when links are configured for operation in 2.048 mbps h-mvip mode, channelised t1/j1/e1 mode or unchannelised mode, the lit block does not perform any translation on the link data. when a link is configured for operation in h-mvip mode, the lit block divides the appropriate clock (rmvck[n] for 2.048 mbps h-mvip and rmv8dc for 8.192 mbps h-mvip) by two and provides this divided down clock to the line interface block. when a link is configured for operation in channelised t1/j1/e1 or unchannelised mode, the lit block does not perform any translation on the link clock. when a link is configured for operation in h-mvip mode, the lit block samples the appropriate frame pulse (rfpb[n] for 2.048 mbps h-mvip and rfp8b for 8.192 mbps h-mvip) and presents the sampled frame pulse to the line interface
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 47 block. when a link is configured for operation in channelised t1/j1/e1 or unchannelised mode, the gapped clock is passed to the lit block unmodified. 8.3.2 line interface there are 32 identical line interface blocks in the rcas672. each line interface block contains 2 sub-bl ocks; one supporting channelised t1/j1/e1 streams and the other h-mvip streams. based on c onfiguration, only one of the sub-blocks are active at one time; the other is held reset. each sub-block contains a bit counter, an 8-bit shift register and a holding register. each sub-block performs serial to parallel conversion. whenever the holding register is updated, a request for service is sent to the priority encoder block. when acknowledged by the priority encoder, the line interface would respond with the data residing in the holding register in the active sub-block. to support h-mvip links, each line interface block contains a time-slot counter. the time-slot counter is incremented each time the holding register is updated. when a frame pulse occurs, the time-slot counter is initialised to indicate that the next bit is the most significant bit of the first time-slot. to support non h-mvip channelised links, each line interface block contains a time-slot counter and a clock activity monitor. the time-slot counter is incremented each time the holding register is updated. the clock activity monitor is a counter that increments at the system clock (sysclk) rate and is cleared by a rising edge of the receive clock (rclk[n]). a framing bit (t1/j1) or a framing byte (e1) is detected when the counter reaches a programmable threshold, in which case, the bit and time-slot counters are initialised to indicate that the next bit is the most significant bit of the first time-slot. for unchannelised links, the time-slot counter and the clock activity monitor are held reset. 8.3.3 priority encoder the priority encoder monitors the line interfaces for requests and synchronises them to the sysclk timing domain. requests are serviced on a fixed priority scheme where highest to lowest priority is assigned from the line interface attached to rd[0] to that attached to rd[31]. thus, simultaneous requests from rd[m] will be serviced ahead of rd[n], if m < n. when there are no pending requests, the priority encoder generates an idle cycle. in addition, once every fourth sysclk cycle, the priority encoder inserts a null cycle where no requests are serviced. this cycle is used by the channel assigner downstream for host microprocessor accesses to the provisioning rams.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 48 8.3.4 channel assigner the channel assigner block determines the channel number of the data byte currently being processed. the block contains a 1024 word channel provision ram. the address of the ram is constructed from concatenating the link number and the time-slot number of the current data byte. the fields of each ram word include the channel number and a time-slot enable flag. the time-slot enable flag labels the current time-slot as belonging to the channel indicted by the channel number field. 8.3.5 loopback controller the loopback controller block implements the channel based diagnostic loopback function. every valid data byte belonging to a channel with diagnostic loopback enabled from the transmit hdlc processor / partial packet buffer block (thdl672) is written into a 64 word fifo. the loopback controller monitors for an idle time-slot or a time-slot carrying a channel with diagnostic loopback enabled. if either conditions hold, the current data byte is replaced by data retrieved from the loopback data fifo. 8.4 receive hdlc processor / partial packet buffer the receive hdlc processor / partial packet buffer block (rhdl672) processes up to 672 synchronous transmission hdlc data streams. each channel can be individually configured to perform flag sequence detection, bit de- stuffing and crc-ccitt or crc-32 verificati on. the packet data is written into the partial packet buffer. at the end of a frame, packet status including crc error, octet alignment error and maximum length violation are also loaded into the partial packet buffer. alternatively, a channel can be provisioned as transparent, in which case, the hdlc data stream is passed to the partial packet buffer processor verbatim. there is a natural precedence in the alarms detectable on a receive packet. once a packet exceeds the programmable maximum packet length, no further processing is performed on it. thus, octet alignment detection, fcs verification and abort recognition are squelched on packets with a maximum length violation. an abort indication squelches octet alignment detection, minimum packet length violations, and fcs verification. in addition, fcs verification is only performed on packets that do not have octet alignment errors, in order to allow the rhdl672 to perform crc calcul ations on a byte-basis. the partial packet buffer is a 32 kbyte ram that is divided into 16-byte blocks. each block has an associated pointer which points to another block. a logical
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 49 fifo is created for each provisioned channel by programming the block pointers to form a circular linked list. a channel fifo can be assigned a minimum of 3 blocks (48 bytes) and a maximum of 2048 bl ocks (32 kbytes). the depth of the channel fifos are monitored in a round-robin fashion. requests are made to the receive any-phy interface block (rapi672) to transfer, on the rx appi, data in channel fifos with depths exceeding their associated threshold. 8.4.1 hdlc processor the hdlc processor is a time-slice state machine which can process up to 672 independent channels. the state vector and provisioning information for each channel is stored in a ram. whenever new channel data arrives, the appropriate state vector is read from the ram, processed and written back to the ram. the hdlc state-machine can be configured to perform flag delineation, bit de-stuffing, crc verification and length monitoring. the resulting hdlc data and status information is passed to the partial packet buffer processor to be stored in the appropriate channel fifo buffer. the configuration of the hdlc processor is accessed using indirect channel read and write operations. when an indirect operation is performed, the information is accessed from ram during a null clock cycle generated by the upstream receive channel assigner block (rcas672). writing new provisioning data to a channel resets the channel's entire state vector. 8.4.2 partial packet buffer processor the partial packet buffer processor controls the 32 kbyte partial packet ram which is divided into 16 byte blocks. a block pointer ram is used to chain the partial packet blocks into circular c hannel fifo buffers. thus, non-contiguous sections of the ram can be allocated in the partial packet buffer ram to create a channel fifo. system software is respons ible for the assignment of blocks to individual channel fifos. figure 4 shows an example of three blocks (blocks 1, 3, and 200) linked together to form a 48 byte channel fifo.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 50 figure 4 ? partial packet buffer structure 16 bytes 16 bytes 16 bytes 16 bytes 16 bytes 16 bytes partial packet buffer ram block 2047 block 0 block 1 block 2 block 3 block 2047 block 0 block 1 block 2 block 3 block pointer ram block 200 block 200 0x03 0xc8 0x01 xx xx xx the partial packet buffer processor is divided into three sections: writer, reader and roamer. the writer is a time-sliced state machine which writes the hdlc data and status information from the hdlc processor into a channel fifo in the packet buffer ram. the reader transfers channel fifo data from the packet buffer ram to the downstream receive any-phy interface block (rapi672). the roamer is a time-sliced state ma chine which tracks channel fifo buffer depths and signals the reader to service a particular channel. if a buffer over-run occurs, the writer ends the current packet from the hdlc processor in the channel fifo with an overrun flag and ignores the rest of the packet. the fifo algorithm of the partial packet buffer processor is based on a programmable per-channel transfer size. instead of tracking the number of full blocks in a channel fifo, the processor tracks the number of transactions. whenever the partial packet writer fills a transfer-sized number of blocks or writes an end-of-packet flag to the channel fifo, a transaction is created. whenever the partial packet reader transmits a tr ansfer-size number of blocks or an end-of- packet flag to the rapi672 block, a transaction is deleted. thus, small packets
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 51 less than the transfer size will be natur ally transferred to the rapi672 block without having to precisely track the num ber of full blocks in the channel fifo. the partial packet roamer performs the transaction accounting for all channel fifos. the roamer increments the transaction count when the writer signals a new transaction and sets a per-channel flag to indicate a non-zero transaction count. the roamer searches the flags in a round-robin fashion to decide for which channel fifo to request transfer by the rapi672 block. the roamer informs the partial packet reader of the channel to process. the reader transfers the data to the rapi672 until the channel transfer size is reached or an end of packet is detected. the reader then informs the roamer that a transaction is consumed. the roamer updates its tr ansaction count and clears the non-zero transaction count flag if required. the roamer then services the next channel with its transaction flag set high. the writer and reader determine empty and full fifo conditions using flags. each block in the partial packet buffer has an associated flag. the writer sets the flag after the block is written and the reader clears the flag after the block is read. the flags are initialized (cleared) when the block pointers are written using indirect block writes. the writer declares a channel fifo overrun whenever the writer tries to store data to a block with a set flag. in order to support optional removal of the fcs from the packet data, the writer does not declare a block as filled (set the block flag nor increment the transaction count) until the first double word of the next block in channel fifo is filled. if the end of a packet resides in the first double word, the writer declares both blocks as full at the same time. when the reader finishes processing a tr ansaction, it examines the first double word of the next block for the end-of-packet flag. if the first double word of the next block contains only fcs bytes, the reader would, optionally, process next transaction (end-of-packet) and consume the bl ock, as it contains information not transferred to the rapi672 block. 8.5 receive any-phy interface the receive any-phy interface (rapi672) provides a low latency path for transferring data out of the partial packet buffer in the rhdl672 and onto the receive any-phy packet interface (rx appi). the rapi672 contains a fifo block for latency control as well as to segregate the appi timing domain from the sysclk timing domain. the rapi672 contains the necessary logic to manage and respond to device polling from an upper layer device. the rapi672 also provides the upper layer device with status information on a per packet basis.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 52 8.5.1 fifo storage and control the fifo block temporarily stores channel data during transfer across the rx appi. rapi672 burst data transfers are transaction based ? a write burst data transfer must be complete before any data will be read, and all data must be completely read from the fifo before any further data will be written into the fifo. to support full rx appi bus rate, a double buffer scheme is used. while data is being read from one fifo onto the rx appi, data can be written into the other fifo. because the bandwidth on the writer side of the fifos is higher than that on the reader side, the rapi672 can maintain continuous full bandwidth transfer over the rx appi. a maximum of 256 bytes can be stored in one of the two fifos for any given burst transfer. a separate storage element samples the 10 bit channel id to associate the data in that fifo with a specific hdlc channel. this channel id is prepended in-band as the first word of every burst data transfer across the rx appi. (the maximum length of a burst data transfer on the rx appi is therefore 129 words, including prepend.) the 3 most significant bits of the prepended word of every burst data tansfer across the rx appi identify the freedm- 32a672 device associated with the transfer and reflect the value of the base address programmed in the rapi672 control register. the writer controller provides a means for writing data into the fifos. the writer controller indicates that it can accept data when there is at least one completely empty fifo. in response, a complete burst transfer of data, up to a maximum of 256 bytes, is written into that empty fifo. (the transfer is sourced by the upstream rhdl672 block which selects from those channels with data available using its round-robin algorithm.) the writer controller then informs the reader controller that data is available in that fifo. the writer controller now switches to the other fifo and repeats the process. when both fifos are full, the writer throttles the upstream rhdl672 block to prevent of any further data writes into the fifos. the reader controller provides a means of reading data out of the fifos onto the rx appi. when selected to do so, and the writer controller has indicated that at least one fifo is full, the reader controlle r will read the data out of the fifos in the order in which they were filled. to prevent from overloading the rx appi with several small bursts of data, the rapi672 automatically deselects after every burst transfer. this provides time for the upper layer device to detect an end of packet indication and possibly reselect a different freedm-32a672 device without having to store the extra word or two which may have been output onto the rx appi during the time it took for deselection.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 53 the rapi672 provides packet status information on the rx appi at the end of every packet transfer. the rapi672 asserts rerr at the end of packet reception (reop high) to indicate that the packet is in error. the rapi672 may be programmed to overwrite rxdata[7:0] of the final word of each packet transfer (reop is high) with the status of packet reception when that packet is errored (rerr is high). overwriting of status information is enabled by setting the staten bit in the rapi control register. 8.5.2 polling control and management the rapi672 only responds to device polls which match the base address programmed in the rapi672 control register. a positive poll response indicates that at least one of the two fifos has a complete xfer[3:0] plus one blocks of data, or an end of packet, and is ready to be selected to transfer this data across the rx appi. 8.6 transmit any-phy interface the transmit any-phy interface (tapi672) provides a low latency path for transferring data from the transmit any-phy packet interface (tx appi) into the partial packet buffer in the thdl672. the tapi672 contains a fifo block for latency control as well as to segregate the appi timing domain from the sysclk timing domain. the tapi672 contains the necessary logic to manage and respond to channel polling from an upper layer device. 8.6.1 fifo storage and control the fifo block temporarily stores channel data during transfer across the tx appi. tapi672 burst data transfers are transaction based on the writer side of the fifo ? all data must be completely read from the fifo before any further data will be written into the fifo. to s upport as close as possi ble to full tx appi bus rate, a double buffer is used. while data is being read from the one fifo, data can be written into the other fifo. because the bandwidth on the reader side of the fifos is higher than that on t he writer side, the tapi672 will not incur any bandwidth reduction to maximum burst data transfers through its fifos. the upper layer device cannot interrupt data transfers on the tx appi. however, the freedm-32a672 may throttle the upper layer device if both fifos in the tapi672 are full. when the fifos in the tapi672 cannot accept data, the tapi672 deasserts the trdy output to the upper layer device connected to the tx appi. in this instance, the upper layer device must halt data transfer until the trdy output is returned high. the upper layer device connected to the tx appi
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 54 must sample the trdy output high before continuing to burst data across the tx appi. a maximum of 256 bytes may be stored in one of the two fifos for any given burst transfer. the first word of each burst transfer contains a prepended address field. (the maximum length of a burst transfer on the tx appi is therefore 129 words, including prepend.) a separate storage element samples the 10 least significant bits of the prepended channel address to associate the data with a specific channel. the 3 most significant bits must match the base address programmed into the tapi672 control register for the tapi672 to respond to the data transaction on the tx appi. the writer controller provides a means for writing data from the tx appi into the fifos. the writer controller can accept data when there is at least one completely empty fifo. when a data transfer begins and there are no empty fifos, the writer controller catches the data provided on the tx appi and throttles the upper layer device. the writ er controller will continue to throttle the upper layer device until at least one fifo is completely empty and can accept a maximum burst transfer of data. the whisper controller provides the channel address of the data being written into the fifo. as soon as the first wo rd of data has been written into the fifo, the whisper controller provides the channel information for that data to the downstream thdl672 block. the whisper controller will wait for acknowledgement and the reader controller is then requested to read the data from the fifo. once the reader controller has commenced the data transfer, the whisper controller will provide the channel information for the other fifo. the whisper controller alternates between the two fifos in the order in which data is written into them. the reader controller provides a means of reading data out of the fifos. when the writer controller indicates that data has been completely written into one of the two fifos, the reader controller is permitted to read that data. the reader controller will then wait for a request for data from the thdl672 block. when requested to transfer data, the reader c ontroller will completely read all the data out of the fifo before indicating to the writer controller that more data may be written into the fifo. because the reader controller reads data out of the fifos in the order in which they were fill ed, the thdl672 block will request data for channels in the order in which they were whispered. the reader controller manages the read and write fifo pointers to allow simultaneous reading and writing of data to/from the double buffer fifo.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 55 8.6.2 polling control and management the tapi672 only responds to poll addresses which are in the range programmed in the base address field in the tapi672 control register. the tapi672 uses the 3 most significant bits of the poll address for device recognition and the 10 least significant bits of the poll address for identification of a channel. the tapi672 provides three poll results for every poll address according to table 7. the tpan[0] bit indicates whether or not space exists in the channel fifo for data and the tpan[1] bit indicates whether or not that polled channel fifo is at risk of underflowing and should be provided data soon. the tpan[2] bit indicates that an underflow event has occurred on that channel fifo. table 7 ? transmit polling poll address tpa1[0] (full/space) tpa1[1] (space/starving) tpa1[2] (underflow) tpa2[0] (full/space) tpa2[1] (space/starving) tpa2[2] (underflow) channel 0 channel 0 channel 0 channel 0 channel 1 channel 1 channel 1 channel 1 channel 1 channel 1 channel 1 channel 2 channel 2 channel 2 channel 2 channel 2 channel 2 channel 2 channel 3 channel 3 channel 3 channel 3 channel 3 channel 3 channel 3 channel 4 channel 4 channel 4 channel 4 channel 4 channel 4 channel 4 channel 5 channel 5 channel 5 channel 5 channel 5 channel 5 channel 5 channel 6 channel 6 channel 6 channel 6 channel 6 channel 6 channel 6 channel 7 channel 7 channel 7 channel 7 channel 7 channel 7 channel 7 channel 8 channel 8 channel 8 channel 8 channel 8 channel 8 channel 8 channel 9 channel 9 channel 9 channel 671 channel 671 channel 671 channel 671 channel 0 channel 0 channel 0 the tapi672 maintains a mirror image of the status of each channel fifo in the partial packet buffer. the thdl672 continuously reports the status of the 672 channel fifos to the tapi672 and the tapi672 updates the mirror image accordingly. the thdl672 also signals to the tapi672 whenever an underflow event has occurred on a channel fifo. at the beginning of every data transfer across the tx appi, the tapi672 sets the mirror image status of the channel to ?full?. only the tapi672 can cause the status to be set to ?full? and only the thdl672 can cause the status to be set to ?space? or ?starving?. only the thdl672 can cause the status to be set to ?underflow? and only the tapi672 can clear the ?underflow? status when that channel fifo is polled. in the event that both the tapi672 and the thdl672 try to change the mirror image status of a
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 56 particular channel simultaneously, the tapi672 takes precedence, except for the ?underflow? status, where the thdl672 takes precedence. 8.7 transmit hdlc controller / partial packet buffer the transmit hdlc controller / partial packet buffer block (thdl672) contains a partial packet buffer for tx appi latency control and a transmit hdlc controller. the thdl672 also contains logic to monitor the full/empty status of each channel fifo and push this status onto the polling interface signals. the thdl672 requests data from the tapi672 in response to control information from the tapi672 indicating the channel for which data is available and ready to be transferred. packet data received from the tapi672 is stored in channel specific fifos residing in the partial packet buffer. when the amount of data in a fifo reaches a programmable threshold, the hdlc controller is enabled to initiate transmission. the hdlc controller performs flag generation, bit stuffing and, optionally, frame check sequence (fcs) insertion. the fcs is software selectable to be crc-ccitt or crc-32. the minimum packet size, excluding fcs, is two bytes. a single byte payl oad is illegal. the hdlc controller delivers data to the transmit channel assigner block (tcas672) on demand. a packet in progress is aborted if an under-run occurs . the thdl672 is programmable to operate in transparent mode where packet data retrieved from the tapi672 is transmitted verbatim. 8.7.1 transmit hdlc processor the hdlc processor is a time-slice state machine which can process up to 672 independent channels. the state vector and provisioning information for each channel is stored in a ram. whenever the tcas672 requests data, the appropriate state vector is read from the ram, processed and finally written back to the ram. the hdlc state-machine can be configured to perform flag insertion, bit stuffing and crc generation. the hdlc processor requests data from the partial packet processor whenever a request for channel data arrives. however, the hdlc processor does not start transmitting a packet until the entire packet is stored in the channel fifo or until the fifo free space is less than the software programmable limit. if a c hannel fifo under-runs, the hdlc processor aborts the packet, generates a microprocessor interrupt and signals the underflow to the transmit any-phy interface. the configuration of the hdlc processor is accessed using indirect channel read and write operations. when an indirect operation is performed, the information is accessed from ram during a null clock cycle inserted by the tcas672 block. writing new provisioning data to a channel resets the channels entire state vector.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 57 8.7.2 transmit partial packet buffer processor the partial packet buffer processor controls the 32 kbyte partial packet ram which is divided into 16 byte blocks. a block pointer ram is used to chain the partial packet blocks into circular c hannel fifo buffers. thus, non-contiguous sections of ram can be allocated in the partial packet buffer ram to create a channel fifo. figure 5 shows an example of three blocks (blocks 1, 3, and 200) linked together to form a 48 byte channel fifo. the three pointer values would be written sequentially using indirect block write accesses. when a channel is provisioned within this fifo, the state machine can be initialized to point to any one of the three blocks. figure 5 ? partial packet buffer structure 16 bytes 16 bytes 16 bytes 16 bytes 16 bytes 16 bytes partial packet buffer ram block 2047 block 0 block 1 block 2 block 3 block 2047 block 0 block 1 block 2 block 3 block pointer ram block 200 block 200 0x03 0xc8 0x01 xx xx xx the partial packet buffer processor is divided into three sections: reader, writer and roamer. the roamer is a time-sliced state machine which tracks each channel?s fifo buffer free space and signals the writer to service a particular channel. the writer requests data from the tapi672 block and transfers packet data from the tapi672 to the associated channel fifo. the reader is a time-
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 58 sliced state machine which transfers the hdlc information from a channel fifo to the hdlc processor in response to a request from the hdlc processor. if a buffer under-run occurs for a channel, t he reader informs the hdlc processor and purges the rest of the packet. if a buffer overflow occurs for a channel, the thdl672 disables the channel as if it were unprovisioned and does not transmit any further data until that channel is reprovisioned. in both cases, an interrupt is generated and the cause of the interrupt may be read via the interrupt status register using the microprocessor interface. the writer and reader determine empty and full fifo conditions using flags. each block in the partial packet buffer has an associated flag. the writer sets the flag after the block is written and the reader clears the flag after the block is read. the flags are initialized (cleared) when the block pointers are written using indirect block writes. the reader declares a channe l fifo under-run whenever it tries to read data from a block without a set flag. the fifo algorithm of the partial packet buffer processor is based on per- channel software programmable transfer size and free space trigger level. instead of tracking the number of full blocks in a channel fifo, the processor tracks the number of empty blocks, called free space, as well as the number of end of packets stored in the fifo. recording the number of empty blocks instead of the number of full blocks r educes the amount of information the roamer must store in its state ram. the partial packet roamer records the fifo free space and end-of-packet count for all channel fifos. when the reader signals that a block has been read, the roamer increments the fifo free space and sets a per-channel request flag if the free space is greater than the limit set by xfer[3:0]. the roamer pushes this status information to the tapi672 to indicate that it can accept at least xfer[3:0] blocks of data. the roamer also dec rements the end-of-packet count when the reader signals that it has passed an end of a packet to the hdlc processor. if the hdlc processor is transmitting a packet and the fifo free space is greater than the free space trigger level and there are no complete packets within the fifo (end-of-packet count equal to zero), a per-channel starving flag is set. the roamer searches the starving flags in a round-robin fashion to decide which channel fifos are at risk of underflowing and pushes this status information to the tapi672. the roamer listens to control information from the tapi672 to decide which channel fifo requests data from the tapi672 block. the roamer informs the partial packet writer of the channel fifo to process and the fifo free space. the writer sends a request for data to the tapi672 block and writes the response data to the channel fifo setting block full flags. the writer reports back to the roamer the num ber of blocks and end-of-pa ckets transferred. the maximum amount of data transferred during one request is limited by a software programmable limit.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 59 the roamer round-robins between all channel fifos and pushes the status to the tapi672 block. the status consists of two pieces of information: (1) is there space in the channel fifo for at least one xfer[3:0] of data, and (2) is this channel fifo at risk of underflowing. where a channel fifo is at risk of underflowing, the thdl672 pushes a starving status for that channel fifo to the tapi672 at the earliest possible opportunity. the configuration of the hdlc processor is accessed using indirect channel read and write operations as well as indirect block read and write operations. when an indirect operation is performed, the information is accessed from ram during a null clock cycle identified by the tcas672 block. writing new provisioning data to a channel resets the entire state vector. 8.8 transmit channel assigner the transmit channel assigner block (tcas672) processes up to 672 channels. data for all channels is sourced from a single byte-serial stream from the transmit hdlc controller / partial packet buffer block (thdl672). the tcas672 demultiplexes the data and assigns each byte to any one of 32 links. each link may be configured to support 2.048 or 8.192 h-mvip traffic, to support t1/j1/e1 channelised traffic or to support unchannelised traffic. when configured to support h-mvip traffic, each group of 8 links share a clock and frame pulse, otherwise each link is independent and has its own associated clock. for each high-speed link (td[2:0]), the tcas provides a six byte fifo. for the remaining links (td[31:3]), the tcas provides a single byte holding register. the tcas672 also performs parallel to serial conversion to form a bit- serial stream. in the event where multiple links are in need of data, tcas672 requests data from upstream blocks on a fixed priority basis with link td[0] having the highest priority and link td[31] the lowest. from the point of view of the tcas672, links configured for h-mvip traffic behave identically to links configured for t1/j1/e1 channelised or unchannelised traffic in the back end, only differing on the link side as described herein. first, the number of time-slots in each frame is programmable to be 32 or 128 and has an associated data clock frequency that is double the data rate. this provides more bandwidth per link for applications requiring higher data densities on a single link. data at each time-slot may be independently assigned to be sourced from a different channel. second, h-mvip links reference the start of each frame with a frame pulse, thereby avoiding having to gap the link clock during the framing bits/bytes of each frame. the frame pulse is provided by an h-mvip bus master and ensures that all agents sharing the h-mvip bus remain synchronized. when configured for operation in 2.048 mbps h-mvip mode, the frame pulse is sampled using the same clock which samples the data. when configured for operation in 8.192 mbps h-mvip mode, the frame pulse is sampled using a
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 60 separate frame pulse clock provided by an h-mvip bus master. the frame pulse clock has a synchronous timing relationship to the data clock. third, not all links are independent. when configured for operation in 2.048 mbps h-mvip mode, each group of 8 links share a clock and a frame pulse. links 0 through 7, 8 through 15, 16 through 23 and 24 through 31 each share a clock and a frame pulse. not all 8 links within each group need to be configured for operation in 2.048 mbps h-mvip mode. however, any link within each logical group of 8 which is configured for 2.048 mbps h-mv ip operation will share the same clock and frame pulse. when configured for operation in 8.192 mbps h-mvip mode, links 4m (0 m 7) share a frame pulse, a data clock and a frame pulse clock. again, not all eight 4m (0 m 7) links need to be configured for operation in 8.192 mbps h-mvip mode, however, any link which is configured for 8.192 mbps h- mvip operation will share the same fr ame pulse, data clock and frame pulse clock. if link 4m is configured for 8.192 mbps h-mvip operation, then data transferred on that link is ?spread? over links 4m, 4m+1 4m+2 and 4m+3 from a channel assigner point of view. accordingly, when link 4m is configured for operation in 8.192 mbps h-mvip mode, links 4m+1, 4m+2 and 4m+3 must also be configured for operation in 8.192 mbps h-mvip mode. in the back end, the tcas672 extracts and processes the time-slots identically to channelised t1/j1/e1 traffic. links containing a t1/j1 or an e1 stream may be channelised. data at each time-slot may be independently assigned to be sourced from a different channel. the link clock is only active during time-slots 1 to 24 of a t1/j1 stream and is inactive during the frame bit. similarly, the clock is only active during time-slots 1 to 31 of an e1 stream and is inactive during the fas and nfas framing bytes. the most significant bit of time-slot 1 of a channelised link is identified by noting the absence of the clock and its re-activation. with knowledge of the transmit link and time-slot identity, the tcas672 performs a table look-up to identify the channel from which a data byte is to be sourced. links may also be unchannelised. then, all data bytes on that link belong to one channel. the tcas672 performs a table look-up to identify the channel to which a data byte belongs using only the outgoing link identity, as no time-slots are associated with unchannelised links. link cl ocks are no longer limited to t1/j1 or e1 rates and may range up to a maximum clock rate of 51.84 mhz for tclk[2:0] and 10 mhz for tclk[31:3]. the link clock is only active during bit times containing data to be transmitted and inactive during bits that are to be ignored by the downstream devices, such as framing and overhead bits. for the case of three unchannelised links, the maximum link rate is 51.84 mhz. for the case of more numerous unchannelised links or a mixture of channelised, unchannelised and h-mvip links, the total instantaneous link rate over all the links is limited to 64 mhz.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 61 8.8.1 line interface translator (lit) the lit block translates the information between the 32 physical links and the line interface block. the lit block performs three functions: data translation, clock translation and frame pulse generation. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode, the lit block translates the data arriving from the line interface block on links 4m, 4m+1, 4m+2 and 4m+3 onto the 128 time-slot link 4m. the lit block translates data arriving from the line interface block on link 4m, 4m+1, 4m+2 and 4m+3 onto time-slots 0 through 31, 32 through 63, 64 through 95 and 96 through 127 respectively. when link 4m is configured for operation in 8.192 mbps h- mvip mode, outputs td[4m+3:4m+1] are driven with constant ones. however, links 4m+1, 4m+2 and 4m+3 must be programmed in the tcas672 link configuration register for 8.192 mbps h-mvip operation. when links are configured for operation in 2.048 mbps h-mvip mode, channelised t1/j1/e1 mode or unchannelised mode, the lit block does not perform any translation on the link data. when a link is configured for operation in h-mvip mode, the lit block divides the appropriate clock (tmvck[n] for 2.048 mbps h-mvip and tmv8dc for 8.192 mbps h-mvip) by two and provides this divided down clock to the line interface block. when a link is configured for operation in channelised t1/j1/e1 or unchannelised mode, the lit block does not perform any translation on the link clock. when a link is configured for operation in h-mvip mode, the lit block samples the appropriate frame pulse (tfpb[n] for 2.048 mbps h-mvip and tfp8b for 8.192 mbps h-mvip) and presents the sampled frame pulse to the line interface block. when a link is configured for operation in channelised t1/j1/e1 or unchannelised mode, the gapped clock is passed to the lit block unmodified. 8.8.2 line interface there are 32 identical line interface blocks in the tcas672. each line interface block contains 2 sub-bl ocks; one supporting channelised t1/j1/e1 streams and the other h-mvip streams. based on c onfiguration, only one of the sub-blocks are active at one time; the other is held reset. each sub-block contains a bit counter, an 8-bit shift register and a holding register. each sub-block performs parallel to serial conversion. whenever the shift register is updated, a request for service is sent to the priority encoder block. when acknowledged by the priority encoder, the line interface would respond by writing the data into the holding register in the active sub-block.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 62 to support h-mvip links, each line interface block contains a time-slot counter. the time-slot counter is incremented each time the holding register is updated. when a frame pulse occurs, the time-slot counter is cleared to indicate that the next byte belongs to the first time-slot. to support non h-mvip channelised links, each line interface block contains a time-slot counter and a clock activity monitor. the time-slot counter is incremented each time the shift register is updated. the clock activity monitor is a counter that increments at the system clock (sysclk) rate and is cleared by a rising edge of the transmit clock (tclk[n]). a framing bit (t1/j1) or a framing byte (e1) is detected when the counter reaches a programmable threshold, at which point, the bit and time-slot counters are initialised to indicate that the next bit sampled is the most significant bit of the first time-slot. for unchannelised links, the time-slot counter and the clock activity monitor are held reset. 8.8.3 priority encoder the priority encoder monitors the line interfaces for requests and synchronises them to the sysclk timing domain. requests are serviced on a fixed priority scheme where highest to lowest priority is assigned from line interface td[0] to line interface td[31]. thus, simultaneous requests from line interface td[m] will be serviced ahead of line interface td[n], if m < n. the priority encoder selects the request from the link with the highest priority for service. when there are no pending requests, the priority encoder generates an idle cycle. in addition, once every fourth sysclk cycle, the priority encoder inserts a null cycle where no requests are serviced. this cycle is used by the channel assigner downstream for cbi accesses to the channel provision ram. 8.8.4 channel assigner the channel assigner block determines the channel number of the request currently being processed. the block contains a 1024 word channel provision ram. the address of the ram is constructed from concatenating the link number and the time-slot number of the highest priority requester. the fields of each ram word include the channel number and a time-slot enable flag. the time-slot enable flag labels the current time-slot as belonging to the channel indicted by the channel number field. for time-slots that are enabled, the channel assigner issues a request to the thdl672 block which responds with packet data within one byte period of the transmit stream.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 63 8.9 performance monitor the performance monitor block (pmon) contains four counters. the first two accumulate receive partial packet buffer fifo overrun events and transmit partial packet buffer fifo underflow events, respectively. the remaining two counters are software programmable to accumulate a variety of events, such as receive packet count, fcs error counts, etc. all counters saturate upon reaching maximum value. the accumulation logic consists of a counter and holding register pair. the counter is incremented when the associated event is detected. writing to the freedm-32a672 master clock / bert activity monitor and accumulation trigger register transfer the count to the corresponding holding register and clear the counter. the contents of the holding register is accessible via the microprocessor interface. 8.10 jtag test access port interface the jtag test access port block provides jtag support for boundary scan. the standard jtag extest, sample, bypass, idcode and stctest instructions are supported. the freedm-32a672 identification code is 073810cd hexadecimal. 8.11 microprocessor interface the freedm-32a672 supports microprocessor access to an internal register space for configuring and monitoring the device. all registers are 16 bits wide but are dword aligned in the microprocessor memory map. the registers are described below: table 8 ? normal mode microprocessor accessible registers address register 0x000 freedm-32a672 master reset 0x004 freedm-32a672 master interrupt enable 0x008 freedm-32a672 master interrupt status 0x00c freedm-32a672 master clock / frame pulse / bert activity monitor and accumulation trigger 0x010 freedm-32a672 master link activity monitor 0x014 freedm-32a672 master line loopback #1 0x018 freedm-32a672 master line loopback #2
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 64 address register 0x01c freedm-32a672 reserved 0x020 freedm-32a672 master bert control 0x024 freedm-32a672 master performance monitor control 0x028 ? 0x0fc reserved 0x100 rcas indirect channel and time-slot select 0x104 rcas indirect channel data 0x108 rcas framing bit threshold 0x10c rcas channel disable 0x110 ? 0x17c rcas reserved 0x180 ? 0x1fc rcas link #0 through #31 configuration 0x200 rhdl indirect channel select 0x204 rhdl indirect channel data register #1 0x208 rhdl indirect channel data register #2 0x20c rhdl reserved 0x210 rhdl indirect block select 0x214 rhdl indirect block data register 0x218 ? 0x21c rhdl reserved 0x220 rhdl configuration 0x224 rhdl maximum packet length 0x228 ? 0x23c rhdl reserved 0x240 ? 0x37c reserved 0x380 thdl indirect channel select 0x384 thdl indirect channel data #1 0x388 thdl indirect channel data #2 0x38c thdl indirect channel data #3 0x390 ? 0x39c thdl reserved 0x3a0 thdl indirect block select 0x3a4 thdl indirect block data
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 65 address register 0x3a8 ? 0x3ac thdl reserved 0x3b0 thdl configuration 0x3b4 ? 0x3bc thdl reserved 0x3c0 ? 0x3fc reserved 0x400 tcas indirect channel and time-slot select 0x404 tcas indirect channel data 0x408 tcas framing bit threshold 0x40c tcas idle time-slot fill data 0x410 tcas channel disable 0x414 ? 0x47c tcas reserved 0x480 ? 0x4fc tcas link #0 through #31 configuration 0x500 pmon status 0x504 pmon receive fifo overflow count 0x508 pmon transmit fifo underflow count 0x50c pmon configurable count #1 0x510 pmon configurable count #2 0x514 ? 0x51c pmon reserved 0x520 ? 0x57c reserved 0x580 rapi control 0x584 ? 0x5bc rapi reserved 0x5c0 ? 0x5fc reserved 0x600 tapi control 0x604 tapi indirect channel provisioning 0x608 tapi indirect channel data register 0x60c ? 0x63c tapi reserved 0x640 ? 0x7fc reserved
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 66 9 normal mode register description normal mode registers are used to configure and monitor the operation of the freedm-32a672. notes on normal mode register bits: 1. writing values into unused register bits has no effect. however, to ensure software compatibility with future, feature-enhanced ve rsions of the pro duct, unused register bits must be written with logic zero. reading back unused bits can produce either a logic one or a logic zero; hence, unused register bits should be masked off by software when read. 2. except where noted, all configuration bits that can be written into can also be read back. this allows the processor c ontrolling the freedm-32a672 to determine the programming state of the block. 3. writable normal mode register bits are cleared to logic zero upon reset unless otherwise noted. 4. writing into read-only normal mode register bit locations does not affect freedm- 32a672 operation unless otherwise noted. 5. certain register bits are reserved. these bits are associated with megacell functions that are unused in this application. to ensure that the freedm-32a672 operates as intended, reserved register bits must only be written with their default values. similarly, writing to reserved registers should be avoided. 9.1 microprocessor accessible registers microprocessor accessible registers can be accessed by the external microprocessor. for each register description below, the hexadecimal register number indicates the address in the freedm-32a672 when accesses are made using the external microprocessor. note these registers are not byte addressable. writing to any one of these registers modifies all 16 bits in the register.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 67 register 0x000 : freedm-32a672 master reset bit type func tion default bit 15 r/w reset 0 bit 14 to bit 12 unused xh bit 11 r type[3] 0 bit 10 r type[2] 0 bit 9 r type[1] 0 bit 8 r type[0] 1 bit 7 r id[7] 0 bit 6 r id[7] 0 bit 5 r id[5] 0 bit 4 r id[4] 0 bit 3 r id[3] 0 bit 2 r id[2] 0 bit 1 r id[1] 1 bit 0 r id[0] 0 this register provides software rese t capability and device id information. reset: the reset bit allows the freedm-32a672 to be reset under software control. if the reset bit is a logic one, the entire freedm-32a672, except the microprocessor interface, is held in reset. this bit is not self-clearing. therefore, a logic zero must be written to bring the freedm-32a672 out of reset. holding the freedm-32a672 in a reset state places it into a low power, stand-by mode. a hardware reset clears the reset bit, thus negating the software reset. note like the hardware reset input (rstb), reset forces the freedm-32a672?s transmit link data pins (td[31:0]) high and the appi outputs tristate.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 68 type[3:0]: the device type bits (type[3:0]) allow software to identify the device as the freedm-32a672 member of the freedm family of products. id[7:0]: the device id bits (id[7:0]) allow software to identify the version level of the freedm-32a672.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 69 register 0x004 : freedm-32a672 master interrupt enable bit type func tion default bit 15 r/w tfudre 0 bit 14 r/w tfovre 0 bit 13 r/w tunpve 0 bit 12 r/w tprtye 0 bit 11 to bit 6 unused xxh bit 5 r/w rfovre 0 bit 4 r/w rpfee 0 bit 3 r/w rabrte 0 bit 2 r/w rfcsee 0 bit 1 unused x bit 0 unused x this register provides interrupt enables for various events detected or initiated by the freedm-32a672. rfcsee: the receive frame check sequence error interrupt enable bit (rfcsee) enables receive fcs error interrupts to the microprocessor. when rfcsee is set high, a mismatch between the received fcs code and the computed crc residue will cause an interrupt to be generated on the intb output. interrupts are masked when rfcsee is set low. however, the rfcsei bit remains valid when interrupts are disabled and may be polled to detect receive fcs error events. rabrte: the receive abort interrupt enable bit (rabrte) enables receive hdlc abort interrupts to the microprocessor. when rabrte is set high, receipt of an abort code (at least 7 contig uous 1?s) will cause an interrupt to be generated on the intb output. interrupts are masked when rabrte is set low. however, the rabrti bit remains valid when interrupts are disabled and may be polled to detect receive abort events.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 70 rpfee: the receive packet format error interrupt enable bit (rpfee) enables receive packet format error interrupts to the microprocessor. when rpfee is set high, receipt of a packet that is longer than the maximum specified in the rhdl maximum packet length register, or a packet that is shorter than 32 bits (crc-ccitt) or 48 bits (crc-32), or a packet that is not octet aligned will cause an interrupt to be generated on the intb output. interrupts are masked when rpfee is set low. however, the rpfei bit remains valid when interrupts are disabled and may be polled to detect receive packet format error events. rfovre: the receive fifo overrun error interrupt enable bit (rfovre) enables receive fifo overrun error interrupts to the microprocessor. when rfovre is set high, attempts to write data into the logical fifo of a channel when it is already full will cause an interrupt to be generated on the intb output. interrupts are masked when rfovre is set low. however, the rfovri bit remains valid when interrupts are disabled and may be polled to detect receive fifo overrun events. tprtye: the transmit parity error interrupt enable bit (tprtye) enables parity errors on the transmit appi to generate interrupts to the microprocessor. when tprtye is set high, detection of a pari ty error on the transmit appi will cause an interrupt to be generated on the intb output. interrupts are masked when tprtye is set low. however, the tprtyi bit remains valid when interrupts are disabled and may be polled to detect parity error events. tunpve: the transmit unprovisioned error interrupt enable bit (tunpve) enables attempted transmissions to unprovisioned channels to generate interrupts to the microprocessor. when tunpve is set high, attempts to write data to an unprovisioned channel will c ause an interrupt to be generated on the intb output. interrupts are masked when tunpve is set low. however, the tunpvi bit remains valid when interrupts are disabled and may be polled to detect attempted transmissions to unprovisioned channel events. tfovre: the transmit fifo overflow error interrupt enable bit (tfovre) enables transmit fifo overflow error interrupts to the microprocessor. when tfovre is set high, attempts to write data to the logical fifo when it is already full will cause an interrupt to be generated on the intb output.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 71 interrupts are masked when tfovre is set low. however, the tfovri bit remains valid when interrupts are disabled and may be polled to detect transmit fifo overflow events. tfudre: the transmit fifo underflow error in terrupt enable bit (tfudre) enables transmit fifo underflow error interrupts to the microprocessor. when tfudre is set high, attempts to read data from the logical fifo when it is already empty will cause an interrupt to be generated on the intb output. interrupts are masked when tfudre is set low. however, the tfudri bit remains valid when interrupts are disabled and may be polled to detect transmit fifo underflow events.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 72 register 0x008 : freedm-32a672 master interrupt status bit type func tion default bit 15 r tfudri x bit 14 r tfovri x bit 13 r tunpvi x bit 12 r tprtyi x bit 11 to bit 6 unused xxh bit 5 r rfovri x bit 4 r rpfei x bit 3 r rabrti x bit 2 r rfcsei x bit 1 unused x bit 0 unused x this register reports the interrupt status for various events detected or initiated by the freedm-32a672. reading this registers acknowledges and clears the interrupts. rfcsei: the receive frame check sequence error interrupt status bit (rfcsei) reports receive fcs error interrupts to the microp rocessor. rfcsei is set high when a mismatch between the received fcs code and the computed crc residue is detected. rfcsei remains valid when interrupts are disabled and may be polled to detect receive fcs error events. rabrti: the receive abort interrupt status bit (rabrti) reports receive hdlc abort interrupts to the microprocessor. rabrti is set high upon receipt of an abort code (at least 7 contiguous 1?s). rabrti remains valid when interrupts are disabled and may be polled to detect receive abort events.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 73 rpfei: the receive packet format error interrupt status bit (rpfei) reports receive packet format error interrupts to the microprocessor. rpfei is set high upon receipt of a packet that is longer than the maximum programmed length, of a packet that is shorter than 32 bits ( crc-ccitt) or 48 bits (crc-32), or of a packet that is not octet aligned. rpfei remains valid when interrupts are disabled and may be polled to detect receive packet format error events. rfovri: the receive fifo overrun error interrupt status bit (rfovri) reports receive fifo overrun error interrupts to the microprocessor. rfovri is set high on attempts to write data into the logical fifo of a channel when it is already full. rfovri remains valid when interrupts are disabled and may be polled to detect receive fifo overrun events. tprtyi: the transmit parity error interrupt status bit (tprtyi) reports the detection of a parity on the transmit appi. tprtyi is set high upon detection of a parity error. tprtyi remains valid when interrupts are disabled and may be polled to detect parity errors. tunpvi: the transmit unprovisioned error interrupt status bit (tunpvi) reports an attempted data transmission to an unprovisioned channel fifo. tunpvi is set high upon attempts to write data to an unprovisioned channel fifo. tunpvi remains valid when interrupts are disabled and may be polled to detect an attempt to write data to an unprovisioned channel fifo. tfovri: the transmit fifo overflow error interrupt status bit (tfovri) reports transmit fifo overflow error interrupts to the microprocessor. tfovri is set high upon attempts to write data to the logical fifo when it is already full. tfovri remains valid when interrupts are disabled and may be polled to detect transmit fifo overflow events. (note ? transmit fifo overflows will not occur if channels are properly polled on the transmit appi before transferring data.) tfudri: the transmit fifo underflow error inte rrupt status bit (tfudri) reports transmit fifo underflow error interrupts to the microprocessor. tfudri is set high upon attempts to read data from the logical fifo when it is already
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 74 empty. tfudri remains valid when interrupts are disabled and may be polled to detect transmit fifo underflow events.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 75 register 0x00c : freedm-32a672 master clock / frame pulse / bert activity monitor and accumulation trigger bit type func tion default bit 15 to bit 14 unused xh bit 13 r txclka x bit 12 r rxclka x bit 11 r tfpa[3] x bit 10 r tfpa[2] x bit 9 r tfpa[1] x bit 8 r tfpa[0] x bit 7 r rfpa[3] x bit 6 r rfpa[2] x bit 5 r rfpa[1] x bit 4 r rfpa[0] x bit 3 r tfp8a x bit 2 r rfp8a x bit 1 r tbda x bit 0 r sysclka x this register provides activity monitoring on the freedm-32a672 system clock, any-phy clocks, h-mvip frame pulse and bert port inputs. when a monitored input makes a transition, t he corresponding register bit is set high. the bit will remain high until this register is read, at which point, all the bits in this register are cleared. a lack of transitions is indicated by the corresponding register bit reading low. this register should be read periodically to detect for stuck at conditions. writing to this register delimits the accumulation intervals in the pmon accumulation registers. counts accumulated in those registers are transferred to holding registers where they can be read. the counters themselves are then cleared to begin accumulating events for a new accumulation interval. the bits in this register are not affected by write accesses.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 76 sysclka: the system clock active bit (sysclka) monitors for low to high transitions on the sysclk input. sysclka is set high on a rising edge of sysclk, and is set low when this register is read. tbda: the transmit bert data active bit (tbda) monitors for low to high transitions on the tbd input. tbda is set high on a rising edge of tdb, and is set low when this register is read. rfp8a: the receive 8.192 mbps h-mvip frame pulse activity bit (rfp8a) monitors for low to high transitions on the rfp8b input. rfp8a is set high when rfp8b has been sampled low and sampled high by falling edges of the rmv8fpc, and is set low when this register is read. tfp8a: the transmit 8.192 mbps h-mvip frame pulse activity bit (tfp8a) monitors for low to high transitions on the tfp8b input. tfp8a is set high when tfp8b has been sampled low and sampled high by falling edges of the tmv8fpc, and is set low when this register is read. rfpa[3:0]: the receive frame pulse activity bits (rfpa[3:0]) monitor for low to high transitions on the rfpb[3:0] inputs. rfpa[n] is set high when rfpb[n] has been sampled low and sampled high by falling edges of the corresponding rmvck[n], and is set low when this register is read. tfpa[3:0]: the transmit frame pulse activity bits (tfpa[3:0]) monitor for low to high transitions on the tfpb[3:0] inputs. tfpa[n] is set high when tfpb[n] has been sampled low and sampled high by falling edges of the corresponding tmvck[n], and is set low when this register is read. rxclka / txclka: the any-phy clock active bits (rxclka, txclka) monitor for low to high transitions on the rxclk and txclk inputs respectively. rxclka and txclka are set high on a rising edge of the corresponding clock, and are set low when this register is read.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 77 register 0x010 : freedm-32a672 master link activity monitor bit type func tion default bit 15 r tlga[7] x bit 14 r tlga[6] x bit 13 r tlga[5] x bit 12 r tlga[4] x bit 11 r tlga[3] x bit 10 r tlga[2] x bit 9 r tlga[1] x bit 8 r tlga[0] x bit 7 r rlga[7] x bit 6 r rlga[6] x bit 5 r rlga[5] x bit 4 r rlga[4] x bit 3 r rlga[3] x bit 2 r rlga[2] x bit 1 r rlga[1] x bit 0 r rlga[0] x this register provides activity monitoring on freedm-32a672 receive and transmit link inputs. when a monitored input makes a low to high transition, the corresponding register bit is set high. the bit will remain high until this register is read, at which point, all the bits in this register are cleared. a lack of transitions is indicated by the corresponding register bit reading low. this register should be read periodically to detect for stuck at conditions. rlga[0]: the receive link group #0 active bit (rlga[0]) monitors for transitions on the rd[3:0] and rclk[3:0]/rmvck[0]/rmv8dc inputs. rlga[0] is set high when either: 1. each of rd[3:0] has been sampled low and sampled high by rising edges of the corresponding rclk[3:0] inputs, or 2. each of rd[3:0] has been sampled low and sampled high by rising edges of the rmvck[0] input, or
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 78 3. rd[0] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[0] is set low when this register is read. rlga[1]: the receive link group #1 active bit (rlga[1]) monitors for transitions on the rd[7:4] and rclk[7:4]/rmvck[0]/rmv8dc inputs. rlga[1] is set high when either: 1. each of rd[7:4] has been sampled low and sampled high by rising edges of the corresponding rclk[7:4] inputs, or 2. each of rd[7:4] has been sampled low and sampled high by rising edges of the rmvck[0] input, or 3. rd[4] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[1] is set low when this register is read. rlga[2]: the receive link group #2 active bit (rlga[2]) monitors for transitions on the rd[11:8] and rclk[11:8]/rmvck[1]/rmv8dc inputs. rlga[2] is set high when either: 1. each of rd[11:8] has been sampled low and sampled high by rising edges of the corresponding rclk[11:8] inputs, or 2. each of rd[11:8] has been sampled low and sampled high by rising edges of the rmvck[1] input, or 3. rd[8] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[2] is set low when this register is read. rlga[3]: the receive link group #3 active bit (rlga[3]) monitors for transitions on the rd[15:12] and rclk[15:12]/rmvck[1]/rmv8dc inputs. rlga[3] is set high when either: 1. each of rd[15:12] has been sampled low and sampled high by rising edges of the corresponding rclk[15:12] inputs, or 2. each of rd[15:12] has been sampled low and sampled high by rising edges of the rmvck[1] input, or 3. rd[12] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[3] is set low when this register is read.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 79 rlga[4]: the receive link group #4 active bit (rlga[4]) monitors for transitions on the rd[19:16] and rclk[19:16]/rmvck[2]/rmv8dc inputs. rlga[4] is set high when either: 1. each of rd[19:16] has been sampled low and sampled high by rising edges of the corresponding rclk[19:16] inputs, or 2. each of rd[19:16] has been sampled low and sampled high by rising edges of the rmvck[2] input, or 3. rd[16] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[4] is set low when this register is read. rlga[5]: the receive link group #5 active bit (rlga[5]) monitors for transitions on the rd[23:20] and rclk[23:20]/rmvck[2]/rmv8dc inputs. rlga[5] is set high when either: 1. each of rd[23:20] has been sampled low and sampled high by rising edges of the corresponding rclk[23:20] inputs, or 2. each of rd[23:20] has been sampled low and sampled high by rising edges of the rmvck[2] input, or 3. rd[20] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[5] is set low when this register is read. rlga[6]: the receive link group #6 active bit (rlga[6]) monitors for transitions on the rd[27:24] and rclk[27:24]/rmvck[3]/rmv8dc inputs. rlga[6] is set high when either: 1. each of rd[27:24] has been sampled low and sampled high by rising edges of the corresponding rclk[27:24] inputs, or 2. each of rd[27:24] has been sampled low and sampled high by rising edges of the rmvck[3] input, or 3. rd[24] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[6] is set low when this register is read. rlga[7]: the receive link group #7 active bit (rlga[7]) monitors for transitions on the rd[31:28] and rclk[31:28]/rmvck[3]/rmv8dc inputs. rlga[7] is set high when either: 1. each of rd[31:28] has been sampled low and sampled high by rising edges of the corresponding rclk[31:28] inputs, or
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 80 2. each of rd[31:28] has been sampled low and sampled high by rising edges of the rmvck[3] input, or 3. rd[28] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[7] is set low when this register is read. tlga[0]: the transmit link group #0 active bit (tlga[0]) monitors for low to high transitions on the tclk[3:0] & tmvck[0] inputs. tlga[0] is set high when either: 1. rising edges have been observed on all four tclk[3:0] inputs, or 2. a rising edge has been observed on the tmvck[0] input. tlga[0] is set low when this register is read. tlga[1]: the transmit link group #1 active bit (tlga[1]) monitors for low to high transitions on the tclk[7:4] & tmvck[1] inputs. tlga[1] is set high when either: 1. rising edges have been observed on all four tclk[7:4] inputs, or 2. a rising edge has been observed on the tmvck[1] input. tlga[1] is set low when this register is read. tlga[2]: the transmit link group #2 active bit (tlga[2]) monitors for low to high transitions on the tclk[11:8] & tmvck[2] inputs. tlga[2] is set high when either: 1. rising edges have been observed on all four tclk[11:8] inputs, or 2. a rising edge has been observed on the tmvck[2] input. tlga[2] is set low when this register is read. tlga[3]: the transmit link group #3 active bit (tlga[3]) monitors for low to high transitions on the tclk[15:12] & tmvck[3] inputs. tlga[3] is set high when either: 1. rising edges have been observed on all four tclk[15:12] inputs, or 2. a rising edge has been observed on the tmvck[3] input. tlga[3] is set low when this register is read. tlga[4]: the transmit link group #4 active bit (tlga[4]) monitors for low to high transitions on the tclk[19:16] inputs. tlga[4] is set high when rising edges
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 81 have been observed on all four tclk[19:16] inputs, and is set low when this register is read. tlga[5]: the transmit link group #5 active bit (tlga[5]) monitors for low to high transitions on the tclk[23:20] inputs. tlga[5] is set high when rising edges have been observed on all four tclk[23:20] inputs, and is set low when this register is read. tlga[6]: the transmit link group #6 active bit (tlga[6]) monitors for low to high transitions on the tclk[27:24] inputs. tlga[6] is set high when rising edges have been observed on all four tclk[27:24] inputs, and is set low when this register is read. tlga[7]: the transmit link group #7 active bit (tlga[7]) monitors for low to high transitions on the tclk[31:28] & tmv8dc inputs. tlga[7] is set high when either: 1. rising edges have been observed on all four tclk[31:28] inputs, or 2. a rising edge has been observed on the tmv8dc input. tlga[7] is set low when this register is read.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 82 register 0x014 : freedm-32a 672 master line loopback #1 bit type func tion default bit 15 r/w llben[15] 0 bit 14 r/w llben[14] 0 bit 13 r/w llben[13] 0 bit 12 r/w llben[12] 0 bit 11 r/w llben[11] 0 bit 10 r/w llben[10] 0 bit 9 r/w llben[9] 0 bit 8 r/w llben[8] 0 bit 7 r/w llben[7] 0 bit 6 r/w llben[6] 0 bit 5 r/w llben[5] 0 bit 4 r/w llben[4] 0 bit 3 r/w llben[3] 0 bit 2 r/w llben[2] 0 bit 1 r/w llben[1] 0 bit 0 r/w llben[0] 0 this register controls line loopback for links #0 to #15. llben[15:0]: the line loopback enable bits (llben[15:0]) controls line loopback for links #15 to #0. when links #0 through #15 are configured for channelised t1/j1/e1 or unchannelised traffic and llben[n] is set high, the data on rd[n] is passed verbatim to td[n] which is then updated on the falling edge of rclk[n]. tclk[n] is ignored. when llben[n] is set low, td[n] is processed normally. line loopback is not supported for h-mvip traffic.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 83 register 0x018 : freedm-32a 672 master line loopback #2 bit type func tion default bit 15 r/w llben[31] 0 bit 14 r/w llben[30] 0 bit 13 r/w llben[29] 0 bit 12 r/w llben[28] 0 bit 11 r/w llben[27] 0 bit 10 r/w llben[26] 0 bit 9 r/w llben[25] 0 bit 8 r/w llben[24] 0 bit 7 r/w llben[23] 0 bit 6 r/w llben[22] 0 bit 5 r/w llben[21] 0 bit 4 r/w llben[20] 0 bit 3 r/w llben[19] 0 bit 2 r/w llben[18] 0 bit 1 r/w llben[17] 0 bit 0 r/w llben[16] 0 this register controls line loopback for links #16 to #31. llben[31:16]: the line loopback enable bits (llben[31:16]) controls line loopback for links #31 to #16. when links #16 through #31 are configured for channelised t1/j1/e1 or unchannelised traffic and llben[n] is set high, the data on rd[n] is passed verbatim to td[n] which is then updated on the falling edge of rclk[n]. tclk[n] is ignored. when llben[n] is set low, td[n] is processed normally. line loopback is not supported for h-mvip traffic.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 84 register 0x01c : freedm-32a672 reserved bit type func tion default bit 15 to bit 1 unused xxxxh bit 0 r/w reserved 0 reserved: the reserved bit must be set low for correct operation of the freedm- 32a672 device.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 85 register 0x020 : freedm-32a672 master bert control bit type func tion default bit 15 r/w tben 0 bit 14 unused x bit 13 unused x bit 12 r/w tbsel[4] 0 bit 11 r/w tbsel[3] 0 bit 10 r/w tbsel[2] 0 bit 9 r/w tbsel[1] 0 bit 8 r/w tbsel[0] 0 bit 7 r/w rben 0 bit 6 unused x bit 5 unused x bit 4 r/w rbsel[4] 0 bit 3 r/w rbsel[3] 0 bit 2 r/w rbsel[2] 0 bit 1 r/w rbsel[1] 0 bit 0 r/w rbsel[0] 0 this register controls the bit error rate testing of the receive and transmit links. bit error rate testing is not supported for links configured for h-mvip traffic. rbsel[4:0]: the receive bit error rates testing link select bits (rbsel[4:0]) controls the source of data on the rbd and rbclk outputs when receive bit error rate testing is enabled (rben set high). rbsel[4:0] is a binary number that selects a receive link configured for non h-mvip traffic (rd[31:0]/rclk[31:0]) to be the source of data for rbd and rbclk outputs. rbsel[4:0] is ignored when rben is set low. rbsel[4:0] cannot select a link configured for h- mvip traffic.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 86 rben: the receive bit error rates testing link enable bit (rben) controls the receive bit error rate testing port. when rben is set high, rbsel[4:0] is a binary number that selects a receive link configured for non h-mvip traffic (rd[31:0]/rclk[31:0]) to be the source of data for rbd and rbclk outputs. when rben is set low, rbd and rbclk are held tristated. tbsel[4:0]: the transmit bit error rates testing link select bits (tbsel[4:0]) controls the over-writing of transmit data on td[31:0] by data on tbd when transmit bit error rate testing is enabled (tben set high) and the selected link is not in line loopback (llben[n] set low). tbsel[4:0] is a binary number that selects a transmit link configured for non h-mvip traffic (td[31:0]/tclk[31:0]) to carry the data on tbd. the tbclk output is a buffered version of the selected one of tclk[31:0]. tbsel[4:0] is ignored when tben is set low. tbsel[4:0] cannot select a link configured for h-mvip traffic. tben: the transmit bit error rates testing link enable bit (tben) controls the transmit bit error rate testing port. when tben is set high and the associated link in not in line loopback (llben set low), tbsel[4:0] is a binary number that selects a transmit link data configured for non h-mvip traffic (td[31:0]) to carry the data on tbd and selects a transmit link clock (tclk[31:0]) as the source of tbclk. when tben is set low, all transmit links are processed normally and tbclk is held tristated.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 87 register 0x024 : freedm-32a672 master performance monitor control bit type func tion default bit 15 unused x bit 14 r/w tp2en 0 bit 13 r/w tabrt2en 0 bit 12 r/w rp2en 0 bit 11 r/w rlene2en 0 bit 10 r/w rabrt2en 0 bit 9 r/w rfcse2en 0 bit 8 r/w rspe2en 0 bit 7 unused x bit 6 r/w tp1en 0 bit 5 r/w tabrt1en 0 bit 4 r/w rp1en 0 bit 3 r/w rlene1en 0 bit 2 r/w rabrt1en 0 bit 1 r/w rfcse1en 0 bit 0 r/w rspe1en 0 this register configures the events that are accumulated in the two configurable performance monitor counters in the pmon block. rspe1en: the receive small packet error accumulate enable bit (rspe1en) enables counting of minimum packet size violation events. when rspe1en is set high, receipt of a packet that is shor ter than 32 bits (crc-ccitt, unspecified crc or no crc) or 48 bits (crc-32) will cause the pmon configurable accumulator #1 register to increment. small packet errors are ignored when rspe1en is set low. rfcse1en: the receive frame check sequence error accumulate enable bit (rfcse1en) enables counting of receive fcs error events. when rfcse1en is set high,
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 88 a mismatch between the received fcs code and the computed crc residue will cause the pmon configurable accumulator #1 register to increment. receive frame check sequence errors are ignored when rfcse1en is set low. rabrt1en: the receive abort accumulate enable bit (rabrt1en) enables counting of receive hdlc abort events. when rabrt1en is set high, receipt of an abort code (at least 7 contiguous 1?s) will cause the pm on configurable accumulator #1 register to increment. receive aborts are ignored when rabrt1en is set low. rlene1en: the receive packet length error accumulate enable bit (rlene1en) enables counting of receive packet length error events. when rlene1en is set high, receipt of a packet that is longer than the programmable maximum or of a packet that in not octet aligned will cause the pm on configurable accumulator #1 register to increment. (receipt of a packet that is both too long and not octet aligned results in only one increment.) receive packet length errors are ignored when rlene1en is set low. rp1en: the receive packet enable bit (rp1en) enables counting of receive error-free packets. when rp1en is set high, rece ipt of an error-free packet will cause the pmon configurable accumulator #1 register to increment. receive error- free packets are ignored when rp1en is set low. tabrt1en: the transmit abort accumulate enable bit (tabrt1en) enables counting of transmit hdlc abort events. when tabrt1en is set high, insertion of an abort in the outgoing stream will cause the pmon configurable accumulator #1 register to increment. transmit aborts are ignored when tabrt1en is set low. tp1en: the transmit packet enable bit (tp1en) enables counting of transmit error-free packets. when tp1en is set high, transmission of an error-free packet will cause the pmon configurable accumulator #1 register to increment. transmit error-free packets are ignored when tp1en is set low.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 89 rspe2en: the receive small packet error accumulate enable bit (rspe2en) enables counting of minimum packet size violation events. when rspe2en is set high, receipt of a packet that is shor ter than 32 bits (crc-ccitt, unspecified crc or no crc) or 48 bits (crc-32) will cause the pmon configurable accumulator #2 register to increment. small packet errors are ignored when rspe2en is set low. rfcse2en: the receive frame check sequence error accumulate enable bit (rfcse2en) enables counting of receive fcs error events. when rfcse2en is set high, a mismatch between the received fcs code and the computed crc residue will cause the pmon configurable accumulator #2 register to increment. receive frame check sequence errors are ignored when rfcse2en is set low. rabrt2en: the receive abort accumulate enable bit (rabrt2en) enables counting of receive hdlc abort events. when rabrt2en is set high, receipt of an abort code (at least 7 contiguous 2?s) will cause the pm on configurable accumulator #2 register to increment. receive aborts are ignored when rabrt2en is set low. rlene2en: the receive packet length error accumulate enable bit (rlene2en) enables counting of receive packet length error events. when rlene2en is set high, receipt of a packet that is longer than the programmable maximum or of a packet that in not octet aligned w ill cause the pm on configurable accumulator #2 register to increment. (receipt of a packet that is both too long and not octet aligned results in only one increment.) receive packet length errors are ignored when rlene2en is set low. rp2en: the receive packet enable bit (rp2en) enables counting of receive error-free packets. when rp2en is set high, rece ipt of an error-free packet will cause the pmon configurable accumulator #2 register to increment. receive error- free packets are ignored when rp2en is set low. tabrt2en: the transmit abort accumulate enable bit (tabrt2en) enables counting of transmit hdlc abort events. when tabrt2en is set high, insertion of an abort in the outgoing stream will cause the pmon configurable accumulator
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 90 #2 register to increment. transmit aborts are ignored when tabrt2en is set low. tp2en: the transmit packet enable bit (tp2en) enables counting of transmit error-free packets. when tp2en is set high, transmission of an error-free packet will cause the pmon configurable accumulator #2 register to increment. transmit error-free packets are ignored when tp2en is set low.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 91 register 0x100 : rcas indirect link and time-slot select bit type func tion default bit 15 r busy x bit 14 r/w rwb 0 bit 13 unused x bit 12 r/w reserved 0 bit 11 r/w reserved 0 bit 10 r/w link[4] 0 bit 9 r/w link[3] 0 bit 8 r/w link[2] 0 bit 7 r/w link[1] 0 bit 6 r/w link[0] 0 bit 5 unused x bit 4 r/w tslot[4] 0 bit 3 r/w tslot[3] 0 bit 2 r/w tslot[2] 0 bit 1 r/w tslot[1] 0 bit 0 r/w tslot[0] 0 this register provides the receive link and time-slot number used to access the channel provision ram. writing to this register triggers an indirect register access. tslot[4:0]: the indirect time-slot number bits (tsl ot[4:0]) indicate the time-slot to be configured or interrogated in the indirect access. for a channelised t1/j1 link, time-slots 1 to 24 are valid. for a channelised e1 link, time-slots 1 to 31 are valid. for an h-mvip link, time-slots 0 to 31 are valid. for unchannelised links, only time-slot 0 is valid. link[4:0]: the indirect link number bits (link[4:0]) select amongst the 32 receive links to be configured or interrogated in the indirect access.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 92 reserved: the reserved bits must be set low for correct operation of the freedm- 32a672 device. rwb: the indirect access control bit (rwb) selects between a configure (write) or interrogate (read) access to the channel provision ram. the address to the channel provision ram is constructed by concatenating the tslot[4:0] and link[4:0] bits. writing a logic zero to rwb triggers an indirect write operation. data to be written is taken from the prov, the cdlben and the chan[9:0] bits of the rcas indirect channel data register. writing a logic one to rwb triggers an indirect read operation. addressing of the ram is the same as in an indirect write operation. the data read can be found in the prov, the cdlben and the chan[9:0] bits of the rcas indirect channel data register. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available in the rcas indirect channel data register or to determine when a new indirect write operation may commence.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 93 register 0x104 : rcas indirect channel data bit type func tion default bit 15 r/w cdlben 0 bit 14 r/w prov 0 bit 13 to bit 10 unused xh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 this register contains the data read from the channel provision ram after an indirect read operation or the data to be inserted into the channel provision ram in an indirect write operation. chan[9:0]: the indirect data bits (chan[9:0]) report the channel number read from the channel provision ram after an indirect read operation has completed. channel number to be written to the channel provision ram in an indirect write operation must be set up in this register before triggering the write. chan[9:0] reflects the value written until the completion of a subsequent indirect read operation. prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from the channel provision ram after an indirect read operation has completed. the provision enable flag to be written to the channel provision ram, in an indirect write operation, must be set up in this register before
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 94 triggering the write. when prov is set high, the current receive data byte is processed as part of the channel as indicated by chan[9:0]. when prov is set low, the current time-slot does not belong to any channel and the receive data byte ignored. prov reflects the value written until the completion of a subsequent indirect read operation. cdlben: the indirect channel based diagnostic loopback enable bit (cdlben) reports the loopback enable flag read from channel provision ram after an indirect read operation has complete. the loopback enable flag to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when cdlben is set high, the current receive data byte is to be over-written by data retrieved from the loopback fifo of the channel as indicated by chan[9:0]. when cdlben is set low, the current receive data byte is processed normally. cdlben reflects the value written until the completion of a subsequent indirect read operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 95 register 0x108 : rcas framing bit threshold bit type func tion default bit 15 to bit 7 unused xxxh bit 6 r/w fthres[6] 0 bit 5 r/w fthres[5] 1 bit 4 r/w fthres[4] 0 bit 3 r/w fthres[3] 0 bit 2 r/w fthres[2] 1 bit 1 r/w fthres[1] 0 bit 0 r/w fthres[0] 1 this register contains the threshold used by the clock activity monitor to detect for framing bits/bytes. fthres[6:0]: the framing bit threshold bits (fthres[6:0]) contains the threshold used by the clock activity monitor to detect for the presence of framing bits. a counter in the clock activity monitor of each receive link increments on each rising edge of sysclk and is cleared, when the bsync bit of that link is set low, by each rising edge of the corresponding rclk[n]. when the bsync bit of that link is set high, the counter is cleared at every fourth rising edge of the corresponding rclk[n]. when the counter exceeds the threshold given by fthres[6:0], a framing bit/byte has been detected. fthres[6:0] should be set as a function of the sysclk period and the expected gapping width of rclk[n] during data bits and during framing bits/bytes. legal range of fthresh[6:0] is ?b0000001 to ?b 1111110. note: for operation with t1/j1 links and sysclk = 45 mhz, fthresh[6:0] should be set to ?b0100101?. the default value of this register reflects this mode of operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 96 register 0x10c : rcas channel disable bit type func tion default bit 15 r/w chdis 0 bit 14 to bit 10 unused xxh bit 9 r/w dchan[9] 0 bit 8 r/w dchan[8] 0 bit 7 r/w dchan[7] 0 bit 6 r/w dchan[6] 0 bit 5 r/w dchan[5] 0 bit 4 r/w dchan[4] 0 bit 3 r/w dchan[3] 0 bit 2 r/w dchan[2] 0 bit 1 r/w dchan[1] 0 bit 0 r/w dchan[0] 0 this register controls the disabling of one specific channel to allow orderly provisioning of time-slots associated with that channel. dchan[9:0]: the disable channel number bits (dchan[9:0]) selects the channel to be disabled. when chdis is set high, t he channel specified by dchan[9:0] is disabled. data in time-slots associated with the specified channel is ignored. when chdis is set low, the channel specified by dchan[9:0] operates normally. chdis: the channel disable bit (chdis) controls the disabling of the channels specified by dchan[9:0]. when chdis is set high, the channel selected by dchan[9:0] is disabled. data in time-slots associated with the specified channel is ignored. when chdis is se t low, the channel specified by dchan[9:0] operates normally.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 97 register 0x180 ? 0x188 : rcas links #0 to #2 configuration bit type func tion default bit 15 to bit 5 unused xxxh bit 4 r/w bsync 0 bit 3 unused x bit 2 r/w mode[2] 0 bit 1 r/w mode[1] 0 bit 0 r/w mode[0] 0 this register configures operational modes of receive links #0 to #2. mode[2:0]: the mode select bits (mode[2:0]) configures the corresponding receive link. table 9 details this procedure. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode (mode[2:0]=?111?), data cannot be received on links 4m+1, 4m+2 and 4m+3. however, links 4m+1, 4m+2 and 4m+3 must be configured for 8.192 mbps h-mvip mode for correct operation of the rcas672. from a channel assignment point of view in the rcas672 (registers 0x100, 0x104), time-slots 0 through 31 of the h-mvip link are treated as time-slots 0 through 31 of link 4m, time-slots 32 through 63 of the h-mvip link are treated as time-slots 0 through 31 of link 4m+1, time-slots 64 through 95 of the h-mvip link are treated as time-slots 0 through 31 of link 4m+2 and time-slots 96 through 127 of the h-mvip link are treated as time- slots 0 through 31 of link 4m+3.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 98 table 9 ? receive links #0 to #2 configuration mode[2:0] link configuration 000 unchannelised 001 channelised t1/j1 (24 time slots labeled 1-24) 010 channelised e1 (31 time slots labeled 1-31) 011 2 mbps h-mvip (32 time slots labeled 0-31) 100 reserved 101 reserved 110 reserved 111 8 mbps h-mvip (128 time slots mapped to time- slots 0 through 31 of links 4m, 4m+1, 4m+2 and 4m+3) bsync: the byte synchronization enable bit (bsync) controls the interpretation of gaps in rclk[n] when link #n is in unchannelised mode (mode[2:0]=?000?). when bsync is set high, the data bit on rd[n] clocked in by the first rising edge of rclk[n] after an extended quiescent period is considered to be the most significant bit of a data byte. when bsync is set low, gaps in rclk[n] carry no special significance. bsync is ignored when mode[2:0] ?000?.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 99 register 0x18c ? 0x1fc : rcas links #3 to #31 configuration bit type func tion default bit 15 to bit 3 unused xxxxh bit 2 r/w mode[2] 0 bit 1 r/w mode[1] 0 bit 0 r/w mode[0] 0 this register configures operational modes of receive links #3 to #31. mode[2:0]: the mode select bits (mode[2:0]) configures the corresponding receive link. table 10 details this procedure. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode (mode[2:0]=?111?), data cannot be received on links 4m+1, 4m+2 and 4m+3. however, links 4m+1, 4m+2 and 4m+3 must be configured for 8.192 mbps h-mvip mode for correct operation of the rcas672. from a channel assignment point of view in the rcas672 (registers 0x100, 0x104), time-slots 0 through 31 of the h-mvip link are treated as time-slots 0 through 31 of link 4m, time-slots 32 through 63 of the h-mvip link are treated as time-slots 0 through 31 of link 4m+1, time-slots 64 through 95 of the h-mvip link are treated as time-slots 0 through 31 of link 4m+2 and time-slots 96 through 127 of the h-mvip link are treated as time- slots 0 through 31 of link 4m+3. table 10 ? receive links #3 to #31 configuration mode[2:0] link configuration 000 unchannelised 001 channelised t1/j1 (24 time slots labeled 1-24) 010 channelised e1 (31 time slots labeled 1-31) 011 2 mbps h-mvip (32 time slots labeled 0-31) 100 reserved 101 reserved 110 reserved 111 8 mbps h-mvip (128 time slots mapped to time- slots 0 through 31 of links 4m, 4m+1, 4m+2 and 4m+3)
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 100 register 0x200 : rhdl indirect channel select bit type func tion default bit 15 r busy x bit 14 r/w crwb 0 bit 13 to bit 10 unused xh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 this register provides the channel number used to access the receive channel provision ram. writing to this register triggers an indirect channel register access. chan[9:0]: the indirect channel number bits (chan[9:0]) indicate the receive channel to be configured or interrogated in the indirect access. crwb: the channel indirect access control bit (crwb) selects between a configure (write) or interrogate (read) access to the receive channel provision ram. writing a logic zero to crwb triggers an indirect write operation. data to be written is taken from the indirect channel data registers. writing a logic one to crwb triggers an indirect read operation. the data read can be found in the indirect channel data registers.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 101 busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operati on is available in the rhdl indirect channel data #1 and #2 registers or to determine when a new indirect write operation may commence.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 102 register 0x204 : rhdl indirect channel data register #1 bit type func tion default bit 15 r/w prov 0 bit 14 r/w strip 0 bit 13 r/w delin 0 bit 12 r tavail x bit 11 w reserved x bit 10 w fptr[10] x bit 9 w fptr[9] x bit 8 w fptr[8] x bit 7 w fptr[7] x bit 6 w fptr[6] x bit 5 w fptr[5] x bit 4 w fptr[4] x bit 3 w fptr[3] x bit 2 w fptr[2] x bit 1 w fptr[1] x bit 0 w fptr[0] x this register contains data read from the channel provision ram after an indirect read operation or data to be inserted into the channel provision ram in an indirect write operation. fptr[10:0]: the indirect fifo block pointer (fptr[10:0]) identifies one of the blocks of the circular linked list in the partial packet buffer used in the logical fifo of the current channel. the fifo pointer to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. the fifo point er value can be any one of the blocks provisioned to form the circular buffer.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 103 reserved: the reserved bit must be set low for correct operation of the freedm- 32a672 device. tavail: the indirect transacti on available bit (tavail) reports the fill level of the partial packet buffer used in the logical fifo of the current channel. tavail is set high when the fifo of the current channel contains sufficient data, as controlled by xfer[3:0], to result in a transfer across the receive appi. tavail is set low when the amount of receive data is too small to result in a transfer across the receive appi. tavail is updated by an indirect channel read operation. delin: the indirect delineate enable bit (delin) configures the hdlc processor to perform flag sequence delineation and bit de-stuffing on the incoming data stream. the delineate enable bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when delin is set high, flag sequence delineation and bit de-stuffing is performed on the incoming data stream. when delin is set low, the hdlc processor does not perform any processing (flag sequence delineation, bit de-stuffing nor crc veri fication) on the incoming stream. delin reflects the value written until the completion of a subsequent indirect channel read operation. strip: the indirect frame check sequence discard bit (strip) configures the hdlc processor to remove the crc from the incoming frame when writing the data to the channel fifo. the fcs discard bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when strip is set high and crc[1:0] is not equal to ?00?, the received crc value is not written to the fifo. when strip is set low, the received crc value is written to the fifo. the bytes in buffer field of the rpd correctly reflect the presence/absence of crc bytes in the buffer. the value of strip is ignored when delin is low. strip reflects the value written until the completion of a subsequent indirect channel read operation. prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from the channel provision ram after an indirect channel read operation has completed. the provision enable flag to be written to the
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 104 channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when prov is set high, the hdlc processor will process data on the c hannel specified by chan[9:0]. when prov is set low, the hdlc proce ssor will ignore data on the channel specified by chan[9:0]. prov reflects the value written until the completion of a subsequent indirect channel read operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 105 register 0x208 : rhdl indirect channel data register #2 bit type func tion default bit 15 r/w 7bit 0 bit 14 r/w priority 0 bit 13 r/w invert 0 bit 12 unused x bit 11 r/w crc[1] 0 bit 10 r/w crc[0] 0 bit 9 r/w offset[1] 0 bit 8 r/w offset[0] 0 bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 r/w xfer[3] 0 bit 2 r/w xfer[2] 0 bit 1 r/w xfer[1] 0 bit 0 r/w xfer[0] 0 this register contains data read from the channel provision ram after an indirect read operation or data to be inserted into the channel provision ram in an indirect write operation. xfer[3:0]: the indirect channel transfer size (xfer[3:0]) configures the amount of data transferred in each transaction. the channel transfer size to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when the channel fifo depth reaches the depth specified by xfer[3:0] or when an end-of-packet exists in the fifo, a poll of this freedm-32a672 device will indicate that data exists and is ready to be transferred across the receive appi. channel transfer size is measured in 16 byte blocks. the amount of data transferred and the depth threshold are specified by given setting is:
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 106 xfer[3:0] + 1 blocks = 16 * (xfer[3:0] + 1) bytes xfer[3:0] should be set such that the num ber of blocks transfe rred is at least two fewer than the total allocated to the associated channel. xfer[3:0] reflects the value written until the completion of a subsequent indirect channel read operation. offset[1:0]: the packet byte offset (offset[1:0]) configures the partial packet processor to insert invalid bytes at the beginning of a packet stored in the channel fifo. the value of offset[1:0] to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. the number of bytes inserted before the beginning of a hdlc packet is defined by the binary value of offset[1:0]. offset[1:0] reflects the value written until the completion of a subsequent indirect channel read operation. crc[1:0]: the crc algorithm bits (crc[1:0]) configures the hdlc processor to perform crc verification on the incoming data stream. the value of crc[1:0] to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. crc[1:0] is ignored when delin is low. crc[1:0] reflects the value written until the completion of a subsequent indirect channel read operation. table 11 ? crc[1:0] settings crc[1] crc[0] operation 0 0 no verification 0 1 crc-ccitt 1 0 crc-32 1 1 reserved invert: the hdlc data inversion bit (invert) configures the hdlc processor to logically invert the incoming hdlc stream from the rcas672 before processing it. the value of invert to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when invert is set to one, the hdlc stream is logically inverted before processing. when invert is set to zero, the hdlc
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 107 stream is not inverted before processing. invert reflects the value written until the completion of a subsequent indirect channel read operation. priority: the channel fifo priority bit (priority) informs the partial packet processor that the channel has precedence over other channels when being serviced by the rapi672 block for transfer across the receive appi. the value of priority to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. channel fifos with priority set to one are serviced by the rapi672 before channel fifos with priority set to zero. channels with an hdlc data rate to fifo size ratio that is significantly higher than other channels should have priority set to one. priority reflects the value written until the completion of a subsequent indirect channel read operation. 7bit: the 7bit enable bit (7bit) configures the hdlc processor to ignore the least significant bit of each octet in the corresponding link rd[n]. the value of 7bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when 7bit is set high, the least significant bit (last bit of each octet received), is ignored. when 7bit is set low, the entire receive data stream is processed. 7bit reflects the value written until the completion of a subsequent indirect channel read operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 108 register 0x210 : rhdl indirect block select bit type func tion default bit 15 r busy x bit 14 r/w brwb x bit 13 unused x bit 12 unused x bit 11 r/w reserved x bit 10 r/w block[10] x bit 9 r/w block[9] x bit 8 r/w block[8] x bit 7 r/w block[7] x bit 6 r/w block[6] x bit 5 r/w block[5] x bit 4 r/w block[4] x bit 3 r/w block[3] x bit 2 r/w block[2] x bit 1 r/w block[1] x bit 0 r/w block[0] x this register provides the block number used to access the block pointer ram. writing to this register triggers an indirect block register access. block[10:0]: the indirect block number (block[10:0]) indicate the block to be configured or interrogated in the indirect access. reserved: the reserved bit must be set low for correct operation of the freedm- 32a672 device. brwb: the block indirect access control bit (brwb) selects between a configure (write) or interrogate (read) access to the block pointer ram. writing a logic
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 109 zero to brwb triggers an indirect block write operation. data to be written is taken from the indirect block data register. writing a logic one to brwb triggers an indirect block read operation. the data read can be found in the indirect block data register. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register should be polled to determine when data from an indirect read operat ion is available in the rhdl indi rect block data register or to determine when a new indirect write operation may commence.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 110 register 0x214 : rhdl indirect block data bit type func tion default bit 15 to bit 12 unused xh bit 11 r/w reserved x bit 10 r/w bptr[10] 0 bit 9 r/w bptr[9] 0 bit 8 r/w bptr[8] 0 bit 7 r/w bptr[7] 0 bit 6 r/w bptr[6] 0 bit 5 r/w bptr[5] 0 bit 4 r/w bptr[4] 0 bit 3 r/w bptr[3] 0 bit 2 r/w bptr[2] 0 bit 1 r/w bptr[1] 0 bit 0 r/w bptr[0] 0 this register contains data read from the block pointer ram after an indirect block read operation or data to be inserted into the block pointer ram in an indirect block write operation. bptr[10:0]: the indirect block pointer (bptr[10:0]) configures the block pointer of the block specified by the indirect block select register. the block pointer to be written to the block pointer ram, in an indirect write operation, must be set up in this register before triggering the write. the block pointer value is the block number of the next block in the linked lis t. a circular list of blocks must be formed in order to use the block list as a receive channel fifo buffer. bptr[10:0] reflects the value written until the completion of a subsequent indirect block read operation. when provisioning a channel fifo, all block pointers must be re-written to properly initialize the fifo.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 111 reserved: the reserved bit must be set low for correct operation of the freedm- 32a672 device.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 112 register 0x220 : rhdl configuration bit type func tion default bit 15 to bit 10 unused xxh bit 9 r/w lenchk 0 bit 8 r/w tstd 0 bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 unused x bit 2 unused x bit 1 unused x bit 0 unused x this register configures all provisioned receive channels. tstd: the telecom standard bit (tstd) controls the bit ordering of the hdlc data transferred across the receive appi. when tstd is set low, the least significant bit of each byte on the receive appi bus (ad[0] and ad[8]) is the first hdlc bit received and the most significant bit of each byte (ad[7] and ad[15]) is the last hdlc bit received (datacom standard). when tstd is set high, ad[0] and ad[8] are the last hdlc bits received and ad[7] and ad[15] are the first hdlc bits received (telecom standard). lenchk: the packet length error check bit (lenchk) controls the checking of receive packets that are longer than the maximum programmed length. when lenchk is set high, receive packets are aborted and the remainder of the frame discarded when the packet exceeds the maximum packet length given by max[15:0]. when lenchk is set low, receive packets are not checked for maximum size and max[15:0] must be set to ?hffff.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 113 register 0x224 : rhdl maximum packet length bit type func tion default bit 15 r/w max[15] 1 bit 14 r/w max[14] 1 bit 13 r/w max[13] 1 bit 12 r/w max[12] 1 bit 11 r/w max[11] 1 bit 10 r/w max[10] 1 bit 9 r/w max[9] 1 bit 8 r/w max[8] 1 bit 7 r/w max[7] 1 bit 6 r/w max[6] 1 bit 5 r/w max[5] 1 bit 4 r/w max[4] 1 bit 3 r/w max[3] 1 bit 2 r/w max[2] 1 bit 1 r/w max[1] 1 bit 0 r/w max[0] 1 this register configures the maximum legal hdlc packet byte length. max[15:0]: the maximum hdlc packet length (max[15:0]) configures the freedm- 32a672 to reject hdlc packets longer than a maximum size when lenchk is set high. receive packets with total length, including address, control, information and fcs fields, greater than max[15:0] bytes are aborted. when lenchk is set low, aborts are not gene rated regardless of packet length and max[15:0] must be set to ?hffff.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 114 register 0x380 : thdl indirect channel select bit type func tion default bit 15 r busy x bit 14 r/w crwb 0 bit 13 to bit 10 unused xh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 this register provides the channel number used to access the transmit channel provision ram. writing to this register triggers an indirect channel register access. chan[9:0]: the indirect channel number bits (chan[9:0]) indicate the channel to be configured or interrogated in the indirect access. crwb: the channel indirect access control bit (crwb) selects between a configure (write) or interrogate (read) access to the channel provision ram. writing a logic zero to crwb triggers an indirect write operation. data to be written is taken from the indirect channel data registers. writing a logic one to crwb triggers an indirect read operation. the data read can be found in the indirect channel data registers.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 115 busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available in the thdl indirect channel data #1, #2 and #3 registers or to determine when a new indirect write operation may commence.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 116 register 0x384 : thdl indirect channel data #1 bit type func tion default bit 15 r/w prov 0 bit 14 r/w crc[1] 0 bit 13 r/w crc[0] 0 bit 12 r/w delin 0 bit 11 w reserved x bit 10 w fptr[10] 0 bit 9 w fptr[9] 0 bit 8 w fptr[8] 0 bit 7 w fptr[7] 0 bit 6 w fptr[6] 0 bit 5 w fptr[5] 0 bit 4 w fptr[4] 0 bit 3 w fptr[3] 0 bit 2 w fptr[2] 0 bit 1 w fptr[1] 0 bit 0 w fptr[0] 0 this register contains data read from the channel provision ram after an indirect channel read operation or data to be inserted into the channel provision ram in an indirect channel write operation. fptr[10:0]: the indirect fifo block pointer (fptr[10:0]) informs the partial packet buffer processor about the circular linked list of blocks to use for a fifo for the channel. the fifo pointer to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. the fifo pointer value can be any one of the block numbers provisioned, by indirect block write operations, to form the circular buffer.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 117 reserved: the reserved bit must be set low for correct operation of the freedm- 32a672 device. delin: the indirect delineate enable bit (delin) configures the hdlc processor to perform flag sequence insertion and bit stuffing on the outgoing data stream. the delineate enable bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when delin is set high, flag sequence insertion, bit stuffing and ,optionally, crc generation is performed on the outgoing hdlc data stream. when delin is set low, the hdlc processor does not perform any processing (flag sequence inserti on, bit stuffing nor crc generation) on the outgoing stream. delin reflects the value written until the completion of a subsequent indirect channel read operation. crc[1:0]: the crc algorithm (crc[1:0]) configures the hdlc processor to perform crc generation on the outgoing hdlc data stream. the value of crc[1:0] to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. crc[1:0] is ignored when delin is low. crc[1:0] reflects the value written until the completion of a subsequent indirect channel read operation. table 12 ? crc[1:0] settings crc[1] crc[0] operation 0 0 no crc 0 1 crc-ccitt 1 0 crc-32 1 1 reserved prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from the channel provision ram after an indirect channel read operation has completed. the provision enable flag to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when prov is set high, the hdlc processor will service requests for data from the tcas672 block. when prov is set low, the hdlc processor will ignore requests from the tcas672
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 118 block. prov reflects the value written until the completion of a subsequent indirect channel read operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 119 register 0x388 : thdl indirect channel data #2 bit type func tion default bit 15 r/w 7bit 0 bit 14 r/w reserved 0 bit 13 r/w invert 0 bit 12 r/w dfcs 0 bit 11 w reserved 0 bit 10 w flen[10] 0 bit 9 w flen[9] 0 bit 8 w flen[8] 0 bit 7 w flen[7] 0 bit 6 w flen[6] 0 bit 5 w flen[5] 0 bit 4 w flen[4] 0 bit 3 w flen[3] 0 bit 2 w flen[2] 0 bit 1 w flen[1] 0 bit 0 w flen[0] 0 this register contains data to be inserted into the channel provision ram in an indirect write operation. flen[10:0]: the indirect fifo length (flen[10:0]) is the number of blocks, less one, that is provisioned to the circular channel fifo specified by the fptr[10:0] block pointer. the fifo length to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. reserved: the reserved bits must be set low for correct operation of the freedm- 32a672 device.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 120 dfcs: the diagnose frame check sequence bit (dfcs) controls the inversion of the fcs field inserted into the transmit packet. the value of dfcs to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when dfcs is set to one, the fcs field in the outgoing hdlc stream is logically inverted allowing diagnosis of downstream fcs verification logic. the outgoing fcs field is not inverted when dfcs is set to zero. dfcs reflects the value written until the completion of a subsequent indirect channel read operation. invert: the hdlc data inversion bit (invert) configures the hdlc processor to logically invert the outgoing hdlc stream. the value of invert to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when invert is set to one, the outgoing hdlc stream is logically in verted. the outgoing hdlc stream is not inverted when invert is set to zero. invert reflects the value written until the completion of a subsequent indirect channel read operation. 7bit: the least significant stuff enable bit (7bit) configures the hdlc processor to stuff the least significant bit of each octet in the corresponding transmit link (td[n]). the value of 7bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when 7bit is set high, the least significant bit (last bit of each octet transmitted) does not cont ain channel data and is forced to the value configured by the bit8 register bit. when 7bit is set low, the entire octet contains valid data and bit8 is ignored. 7bit reflects the value written until the completion of a subsequent indirect channel read operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 121 register 0x38c : thdl indirect channel data #3 bit type func tion default bit 15 r/w trans 0 bit 14 r/w idle 0 bit 13 unused x bit 12 unused x bit 11 r/w level[3] 0 bit 10 r/w level[2] 0 bit 9 r/w level[1] 0 bit 8 r/w level[0] 0 bit 7 r/w flag[2] 0 bit 6 r/w flag[1] 0 bit 5 r/w flag[0] 0 bit 4 unused x bit 3 r/w xfer[3] 0 bit 2 r/w xfer[2] 0 bit 1 r/w xfer[1] 0 bit 0 r/w xfer[0] 0 this register contains data read from the channel provision ram after an indirect read operation or data to be inserted into the channel provision ram in an indirect write operation. xfer[3:0]: the indirect channel transfer size (xfer[3:0]) specifies the amount of data the partial packet processor requests from the tapi672 block. the channel transfer size to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when the channel fifo free space reaches or exceeds the limit specified by xfer[3:0], the partial packet processor will inform the tapi672 so that a poll on that channel reflects that the channel fifo is able to accept xfer[3:0] + 1 blocks of data. fifo free space and tr ansfer size are meas ured in number of 16-byte blocks. xfer[3:0] reflects the value written until the completion of a subsequent indirect channel read operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 122 to prevent lockup, the channel transfer size (xfer[3:0]) can be configured to be less than or equal to the start transmission level set by level[3:0] and trans. alternatively, the channel transfer size can be set such that the total number of blocks in the logical channel fifo minus the start transmission level is an integer multiple of the channel transfer size. flag[2:0]: the flag insertion control (flag[2:0]) configures the minimum number of flags or bytes of idle bits the hdlc processor inserts between hdlc packets. the value of flag[2:0] to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. the minimum number of flags or bytes of idle (8 bits of 1?s) inserted between hdlc packets is shown in the table below. flag[2:0] reflects the value written until the completion of a subsequent indirect channel read operation. table 13 ? flag[2:0] settings flag[2:0] minimum number of flag/idle bytes 000 1 flag / 0 idle byte 001 2 flags / 0 idle byte 010 4 flags / 2 idle bytes 011 8 flags / 6 idle bytes 100 16 flags / 14 idle bytes 101 32 flags / 30 idle bytes 110 64 flags / 62 idle bytes 111 128 flags / 126 idle bytes level[3:0]: the indirect channel fifo trigger level (level[3:0]), in concert with the trans bit, configure the various channel fifo free space levels which trigger the hdlc processor to start transmission of a hdlc packet as well as trigger the partial packet buffer to request data from the tapi672 as shown in the following table. the channel fifo trigger level to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. level[3:0] reflects the value written until the completion of a subsequent indirect channel read operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 123 the hdlc processor starts transmitting a packet when the channel fifo free space is less than or equal to the level specified in the appropriate start transmission level column of the following table or when an end of a packet is stored in the channel fifo. when the channel fifo free space is greater than or equal to the level specified in the starving trigger level column of the following table and the hdlc processor is transmitting a packet and an end of a packet is not stored in the channel fifo, the partial packet buffer makes expedited requests to the tapi672 to re trieve xfer[3:0] + 1 blocks of data. to prevent lockup, the channel transfer size (xfer[3:0]) can be configured to be less than or equal to the start transmission level set by level[3:0] and trans. alternatively, the channel transfer size can be set such that the total number of blocks in the logical channel fifo, minus the start transmission level, is an integer multiple of the channel transfer size. the starving trigger level must always be set to a number of blocks greater than or equal to the channel transfer size. idle: the interframe time fill bit (idle) configures the hdlc processor to use flag bytes or hdlc idle as the interframe time fill between hdlc packets. the value of idle to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when idle is set low, the hdlc processor uses flag bytes as the interframe time fill. when idle is set high, the hdlc processor uses hdlc idle (all one?s bit with no bit-stuffing pattern is transmitted) as the interframe time fill. idle reflects the value written until the completion of a subsequent indirect channel read operation. trans: the indirect transmission start bit (trans), in concert with the level[3:0] bits, configure the various channel fifo free space levels which trigger the hdlc processor to start transmission of a hdlc packet as well as trigger the partial packet buffer to request data from the tapi672 as shown in the following table. the transmission start mode to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. trans reflects the value written until the completion of a subsequent indirect channel read operation. the hdlc processor starts transmitting a packet when the channel fifo free space is less than or equal to the level specified in the appropriate start transmission level column of the following table or when an end of a packet is stored in the channel fifo. when the channel fifo free space is greater than or equal to the level specified in the starving trigger level column of the
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 124 following table and the hdlc processor is transmitting a packet and an end of a packet is not stored in the channel fifo, the partial packet buffer makes expedited requests to the tapi672 to re trieve xfer[3:0] + 1 blocks of data. to prevent lockup, the channel transfer size (xfer[3:0]) can be configured to be less than or equal to the start transmission level set by level[3:0] and trans. alternatively, the channel transfer size can be set, such that, the total number of blocks in the logi cal channel fifo minus the start transmission level is an integer multiple of the channel transfer size. the starving trigger level must always be se t to a number of bl ocks greater than or equal to the channel transfer size. table 14 ? level[3:0]/trans settings level[3:0] starving trigger level start transmission level (trans=0) start transmission level (trans=1) 0000 2 blocks (32 bytes free) 1 block (16 bytes free) 1 block (16 bytes free) 0001 3 blocks (48 bytes free) 2 blocks (32 bytes free) 1 block (16 bytes free) 0010 4 blocks (64 bytes free) 3 blocks (48 bytes free) 2 blocks (32 bytes free) 0011 6 blocks (96 bytes free) 4 blocks (64 bytes free) 3 blocks (48 bytes free) 0100 8 blocks (128 bytes free) 6 blocks (96 bytes free) 4 blocks (64 bytes free) 0101 12 blocks (192 bytes free) 8 blocks (128 bytes free) 6 blocks (96 bytes free) 0110 16 blocks (256 bytes free) 12 blocks (192 bytes free) 8 blocks (128 bytes free) 0111 24 blocks (384 bytes free) 16 blocks (256 bytes free) 12 blocks (192 bytes free) 1000 32 blocks (512 bytes free) 24 blocks (384 bytes free) 16 blocks (256 bytes free) 1001 48 blocks (768 bytes free) 32 blocks (512 bytes free) 24 blocks (384 bytes free)
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 125 level[3:0] starving trigger level start transmission level (trans=0) start transmission level (trans=1) 1010 64 blocks (1 kbytes free) 48 blocks (768 bytes free) 32 blocks (512 bytes free) 1011 96 blocks (1.5 kbytes free) 64 blocks (1 kbytes free) 48 blocks (768 bytes free) 1100 192 blocks (3 kbytes free) 128 blocks (2 kbytes free) 96 blocks (1.5 kbytes free) 1101 384 blocks (6 kbytes free) 256 blocks (4 kbytes free) 192 blocks (2 kbytes free) 1110 768 blocks (12 kbytes free) 512 blocks (8 kbytes free) 384 blocks (4 kbytes free) 1111 1536 blocks (24 kbytes free) 1024 blocks (16 kbytes free) 768 blocks (8 kbytes free)
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 126 register 0x3a0 : thdl indirect block select bit type func tion default bit 15 r busy x bit 14 r/w brwb 0 bit 13 to bit 12 unused xh bit 11 r/w reserved x bit 10 r/w block[10] 0 bit 9 r/w block[9] 0 bit 8 r/w block[8] 0 bit 7 r/w block[7] 0 bit 6 r/w block[6] 0 bit 5 r/w block[5] 0 bit 4 r/w block[4] 0 bit 3 r/w block[3] 0 bit 2 r/w block[2] 0 bit 1 r/w block[1] 0 bit 0 r/w block[0] 0 this register provides the block number used to access the block pointer ram. writing to this register triggers an indirect block register access. block[10:0]: the indirect block number (block[10:0]) indicate the block to be configured or interrogated in the indirect access. reserved: the reserved bit must be set low for correct operation of the freedm- 32a672 device. brwb: the block indirect access control bit (brwb) selects between a configure (write) or interrogate (read) access to the block pointer ram. writing a logic
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 127 zero to brwb triggers an indirect block write operation. data to be written is taken from the indirect block data register. writing a logic one to brwb triggers an indirect block read operation. the data read can be found in the indirect block data register. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register should be polled to determine when data from an indirect read operation is available in the thdl indirect block data register or to determine when a new indirect write operation may commence.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 128 register 0x3a4 : thdl indirect block data bit type func tion default bit 15 r/w reserved 0 bit 14 to bit 12 unused xh bit 11 r/w reserved x bit 10 r/w bptr[10] 0 bit 9 r/w bptr[9] 0 bit 8 r/w bptr[8] 0 bit 7 r/w bptr[7] 0 bit 6 r/w bptr[6] 0 bit 5 r/w bptr[5] 0 bit 4 r/w bptr[4] 0 bit 3 r/w bptr[3] 0 bit 2 r/w bptr[2] 0 bit 1 r/w bptr[1] 0 bit 0 r/w bptr[0] 0 this register contains data read from the transmit block pointer ram after an indirect block read operation or data to be inserted into the transmit block pointer ram in an indirect block write operation. bptr[10:0]: the indirect block pointer (bptr[10:0]) configures the block pointer of the block specified by the indirect block select register. the block pointer to be written to the transmit block pointer ram, in an indirect write operation, must be set up in this register before triggering the write. the block pointer value is the block number of the next block in t he linked list. a circular list of blocks must be formed in order to use the block list as a channel fifo buffer. fptr[10:0] reflects the value written until the completion of a subsequent indirect block read operation. when provisioning a channel fifo, all blocks pointers must be re-written to properly initialize the fifo.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 129 reserved: the reserved bits (reserved) must be set low for correct operation of the freedm-32a672 device.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 130 register 0x3b0 : thdl configuration bit type func tion default bit 15 to bit 10 unused xxh bit 9 r/w bit8 0 bit 8 r/w tstd 0 bit 7 r/w reserved 0 bit 6 to bit 4 unused xh bit 3 to bit 0 r/w reserved 0h this register configures all provisioned channels. reserved: the reserved bits must be set low for correct operation of the freedm- 32a672 device. tstd: the telecom standard bit (tstd) controls the bit ordering of the hdlc data transferred on the transmit appi. when tstd is set low, the least significant bit of the each byte on the transmit appi bus (ad[0] and ad[8]) is the first hdlc bit transmitted and the most significant bit of each byte (ad[7] and ad[15]) is the last hdlc bit transmitted (datacom standard). when tstd is set high, ad[0] and ad[8] are the last hdlc bit transmitted and ad[7] and ad[15] are the first hdlc bit transmitted (telecom standard). bit8: the least significant stuff control bit (bit8) carries the value placed in the least significant bit of each octet when the hdlc processor is configured (7bit set high) to stuff the least significant bit of each octet in the corresponding transmit link (td[n]). when bit8 is set high, the least significant bit (last bit of each octet transmitted) is forced high. when bit8 is set low, the least significant bit is forced low. bit8 is ignored when 7bit is set low.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 131 register 0x400 : tcas indirect link and time-slot select bit type func tion default bit 15 r busy x bit 14 r/w rwb 0 bit 13 unused x bit 12 r/w reserved 0 bit 11 r/w reserved 0 bit 10 r/w link[4] 0 bit 9 r/w link[3] 0 bit 8 r/w link[2] 0 bit 7 r/w link[1] 0 bit 6 r/w link[0] 0 bit 5 unused x bit 4 r/w tslot[4] 0 bit 3 r/w tslot[3] 0 bit 2 r/w tslot[2] 0 bit 1 r/w tslot[1] 0 bit 0 r/w tslot[0] 0 this register provides the link number and time-slot number used to access the transmit channel provision ram. writing to this register triggers an indirect register access and transfers the contents of the indirect channel data register to an internal holding register. tslot[4:0]: the indirect time-slot number bits (tsl ot[4:0]) indicate the time-slot to be configured or interrogated in the indirect access. for a channelised t1/j1 link, time-slots 1 to 24 are valid. for a channelised e1 link, time-slots 1 to 31 are valid. for a h-mvip link, time-slots 0 to 31 are valid. for unchannelised links, only time-slot 0 is valid.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 132 link[4:0]: the indirect link number bits (link[4:0]) select amongst the 32 transmit links to be configured or interrogated in the indirect access. reserved: the reserved bits must be set low for correct operation of the freedm- 32a672 device. rwb: the indirect access control bit (rwb) selects between a configure (write) or interrogate (read) access to the transmit channel provision ram. the address to the transmit channel provision ram is constructed by concatenating the tslot[4:0] and link[4:0] bits. writing a logic zero to rwb triggers an indirect write operation. data to be written is taken from the prov and the chan[9:0] bits of the indirect data register. writing a logic one to rwb triggers an indirect read operation. addressing of the ram is the same as in an indirect write operation. the data read can be found in the prov and the chan[9:0] bits of the indirect channel data register. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available in the tcas indirect channel data register or to determine when a new indirect write operation may commence.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 133 register 0x404 : tcas indirect channel data bit type func tion default bit 15 r/w prov 0 bit 14 to bit 10 unused xxh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 this register contains the data read from the transmit channel provision ram after an indirect read operation or the data to be inserted into the transmit channel provision ram in an indirect write operation. chan[9:0]: the indirect data bits (chan[9:0]) report the channel number read from the transmit channel provision ram after an indirect read operation has completed. channel number to be written to the transmit channel provision ram in an indirect write operation must be set up in this register before triggering the write. chan[9:0] reflects the value written until the completion of a subsequent indirect read operation. prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from transmit channel provision ram after an indirect read operation has completed. the provision enable flag to be written to the transmit channel provision ram in an indirect write operation must be set up in this register before triggering the write. when prov is set high, the current time-
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 134 slot is assigned to the channel as indicated by chan[9:0]. when prov is set low, the time-slot does not belong to any channel. the transmit link data is set to the contents of the idle time-slot fill data register. prov reflects the value written until the completion of a subsequent indirect read operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 135 register 0x408 : tcas framing bit threshold bit type func tion default bit 15 to bit 7 unused xxxh bit 6 r/w fthres[6] 0 bit 5 r/w fthres[5] 1 bit 4 r/w fthres[4] 0 bit 3 r/w fthres[3] 0 bit 2 r/w fthres[2] 1 bit 1 r/w fthres[1] 0 bit 0 r/w fthres[0] 1 this register contains the threshold used by the clock activity monitors to detect for framing bits/bytes. fthres[6:0]: the framing bit threshold bits (fthres[6:0]) contains the threshold used by the clock activity monitor to detect for the presence of framing bits. a counter in the clock activity monitor of each receive link increments on each rising edge of sysclk and is cleared, when the bsync bit of that link is set low, by each rising edge of the corresponding tclk[n]. when the bsync bit of that link is set high, the counter is cleared at every fourth rising edge of the corresponding tclk[n]. when the counter exceeds the threshold given by fthres[6:0], a framing bit/byte has been detected. fthres[6:0] should be set as a function of the sysclk period and the expected gapping width of tclk[n] during data bits and during framing bits/bytes. legal range of fthres[6:0] is ?b0000001 to ?b1111110. note: for operation with t1/j1 links and sysclk = 45 mhz, fthresh[6:0] should be set to ?b0100101?. the default value of this register reflects this mode of operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 136 register 0x40c : tcas idle time-slot fill data bit type func tion default bit 15 to bit 8 unused xxh bit 7 r/w fdata[7] 1 bit 6 r/w fdata[6] 1 bit 5 r/w fdata[5] 1 bit 4 r/w fdata[4] 1 bit 3 r/w fdata[3] 1 bit 2 r/w fdata[2] 1 bit 1 r/w fdata[1] 1 bit 0 r/w fdata[0] 1 this register contains the data to be written to disabled time-slots of a channelised link. fdata[7:0]: the fill data bits (fdata[7:0]) are transmitted during disabled (prov set low) time-slots of channelised links.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 137 register 0x410 : tcas channel disable bit type func tion default bit 15 r/w chdis 0 bit 14 to bit 10 unused xxh bit 9 r/w dchan[9] 0 bit 8 r/w dchan[8] 0 bit 7 r/w dchan[7] 0 bit 6 r/w dchan[6] 0 bit 5 r/w dchan[5] 0 bit 4 r/w dchan[4] 0 bit 3 r/w dchan[3] 0 bit 2 r/w dchan[2] 0 bit 1 r/w dchan[1] 0 bit 0 r/w dchan[0] 0 this register controls the disabling of one specific channel to allow orderly provisioning of time-slots. dchan[9:0]: the disable channel number bits (dchan[9:0]) selects the channel to be disabled. when chdis is set high, t he channel specified by dchan[9:0] is disabled. data in time-slots associated with the specified channel is set to fdata[7:0] in the idle time-slot fill data register. when chdis is set low, the channel specified by dcha n[9:0] operates normally. chdis: the channel disable bit (chdis) controls the disabling of the channels specified by dchan[9:0]. when chdis is set high, the channel selected by dchan[9:0] is disabled. data in time-slots associated with the specified channel is set to fdata[7:0] in the id le time-slot fill data register. when chdis is set low, the channel specif ied by dchan[9:0] operates normally.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 138 register 0x480 ? 0x488 : tcas links #0 to #2 configuration bit type func tion default bit 15 to bit 5 unused xxxh bit 4 r/w bsync 0 bit 3 unused x bit 2 r/w mode[2] 0 bit 1 r/w mode[1] 0 bit 0 r/w mode[0] 0 this register configures operational modes of transmit links #0 to #2. mode[2:0]: the mode select bits (mode[2:0]) configures the corresponding transmit link. table 15 details this procedure. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode, links 4m+1, 4m+2 and 4m+3 are driven with constant ones. however, links 4m+1, 4m+2 and 4m+3 must be configured for 8.192 mbps h-mvip mode for correct operation of the tcas672. from a channel assignment point of view in the tcas672 (registers 0x400, 0x404), time-slots 0 through 31 of link 4m are mapped to time-slots 0 through 31 of the h-mvip link, time-slots 0 through 31 of link 4m+1 are mapped to time-slots 32 through 63 of the h-mvip link, time-slots 0 through 31 of link 4m+2 are mapped to time-slots 64 through 95 of the h- mvip link and time-slots 0 through 31 of link 4m+3 are mapped to time-slots 96 through 127 of the h-mvip link.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 139 table 15 ? transmit links #0 to #2 configuration mode[2:0] link configuration 000 unchannelised 001 channelised t1/j1 (24 time slots labeled 1-24) 010 channelised e1 (31 time slots labeled 1-31) 011 2 mbps h-mvip (32 time slots labeled 0-31) 100 reserved 101 reserved 110 reserved 111 8 mbps h-mvip (128 time slots mapped to time- slots 0 through 31 of links 4m, 4m+1, 4m+2 and 4m+3) bsync: the byte synchronization enable bit (bsync) controls the interpretation of gaps in tclk[n] when link #n is in unchannelised mode (mode[2:0]=?000?). when bsync is set high, the data bit on td[n] clocked in by a downstream device on the first rising edge of tclk[n] after an extended quiescent period is considered to be the most significant bit of a data byte. when bsync is set quiescent, gaps in tclk[n] carry no special significance. bsync is ignored when mode[2:0] ?000?.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 140 register 0x48c ? 0x4fc : tcas links #3 to #31 configuration bit type func tion default bit 15 to bit 3 unused xxxxh bit 2 r/w mode[2] 0 bit 1 r/w mode[1] 0 bit 0 r/w mode[0] 0 this register configures operational modes of transmit links #3 to #31. mode[2:0]: the mode select bits (mode[2:0]) configures the corresponding transmit link. table 16 details this procedure. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode, links 4m+1, 4m+2 and 4m+3 are driven with constant ones. however, links 4m+1, 4m+2 and 4m+3 must be configured for 8.192 mbps h-mvip mode for correct operation of the tcas672. from a channel assignment point of view in the tcas672 (registers 0x100, 0x104), time-slots 0 through 31 of link 4m are mapped to time-slots 0 through 31 of the h-mvip link, time-slots 0 through 31 of link 4m+1 are mapped to time-slots 32 through 63 of the h-mvip link, time-slots 0 through 31 of link 4m+2 are mapped to time-slots 64 through 95 of the h- mvip link and time-slots 0 through 31 of link 4m+3 are mapped to time-slots 96 through 127 of the h-mvip link. table 16 ? transmit links #3 to #31 configuration mode[2:0] link configuration 000 unchannelised 001 channelised t1/j1 (24 time slots labeled 1-24) 010 channelised e1 (31 time slots labeled 1-31) 011 2 mbps h-mvip (32 time slots labeled 0-31) 100 reserved 101 reserved 110 reserved 111 8 mbps h-mvip (128 time slots mapped to time- slots 0 through 31 of links 4m, 4m+1, 4m+2 and 4m+3)
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 141 register 0x500 : pmon status bit type func tion default bit 15 to bit 6 unused xxxh bit 5 r c2det x bit 4 r c1det x bit 3 r ufdet x bit 2 r ofdet x bit 1 unused x bit 0 unused x this register contains status information indicating whether a non-zero count has been latched in the count registers. ofdet: the overflow detect bit (ofdet) indicates the status of the pmon receive fifo overflow count register. ofdet is set high when overflow events have occurred during the latest pmon accumula tion interval. ofdet is set low if no overflow events are detected. ufdet: the underflow detect bit (ufdet) indicates the status of the pmon transmit fifo underflow count register. ufdet is set high when underflow events have occurred during the latest pmon accumulation interval. ufdet is set low if no underflow events are detected. c1det: the configurable event #1 detect bit (c1det) indicates the status of the pmon configurable count #1 register. c1det is set high when selected events have occurred during the latest pmon accumulation interval. c1det is set low if no selected events are detected. c2det: the configurable event #2 detect bit (c2det) indicates the status of the pmon configurable count #2 register. c2det is set high when selected
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 142 events have occurred during the latest pmon accumulation interval. c2det is set low if no selected events are detected.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 143 register 0x504 : pmon receive fifo overflow count bit type func tion default bit 15 r of[15] x bit 14 r of[14] x bit 13 r of[13] x bit 12 r of[12] x bit 11 r of[11] x bit 10 r of[10] x bit 9 r of[9] x bit 8 r of[8] x bit 7 r of[7] x bit 6 r of[6] x bit 5 r of[5] x bit 4 r of[4] x bit 3 r of[3] x bit 2 r of[2] x bit 1 r of[1] x bit 0 r of[0] x this register reports the number of receive fifo overflow events in the previous accumulation interval. of[15:0]: the of[15:0] bits reports the number of receive fifo overflow events that have been detected since the last time this register was polled. this register is polled by writing to the freedm-32a672 master clock / bert activity monitor and accumulation trigger register. the write access transfers the internally accumulated error count to the fifo overflow register and simultaneously resets the internal counter to begin a new cycle of error accumulation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 144 register 0x508 : pmon transm it fifo underflow count bit type func tion default bit 15 r uf[15] x bit 14 r uf[14] x bit 13 r uf[13] x bit 12 r uf[12] x bit 11 r uf[11] x bit 10 r uf[10] x bit 9 r uf[9] x bit 8 r uf[8] x bit 7 r uf[7] x bit 6 r uf[6] x bit 5 r uf[5] x bit 4 r uf[4] x bit 3 r uf[3] x bit 2 r uf[2] x bit 1 r uf[1] x bit 0 r uf[0] x this register reports the number of transmit fifo underflow events in the previous accumulation interval. uf[15:0]: the uf[15:0] bits reports the number of transmit fifo underflow events that have been detected since the last time this register was polled. this register is polled by writing to the freedm-32a672 master clock / bert activity monitor and accumulation trigger register. the write access transfers the internally accumulated error count to the fifo underflow register and simultaneously resets the internal counter to begin a new cycle of error accumulation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 145 register 0x50c : pmon c onfigurable count #1 bit type func tion default bit 15 r c1[15] x bit 14 r c1[14] x bit 13 r c1[13] x bit 12 r c1[12] x bit 11 r c1[11] x bit 10 r c1[10] x bit 9 r c1[9] x bit 8 r c1[8] x bit 7 r c1[7] x bit 6 r c1[6] x bit 5 r c1[5] x bit 4 r c1[4] x bit 3 r c1[3] x bit 2 r c1[2] x bit 1 r c1[1] x bit 0 r c1[0] x this register reports the number events, selected by the freedm-32a672 master performance monitor control register, that occurred in the previous accumulation interval. c1[15:0]: the c1[15:0] bits reports the number of selected events that have been detected since the last time this register was polled. this register is polled by writing to the freedm-32a672 master clock / bert activity monitor and accumulation trigger register. the write access transfers the internally accumulated error count to the configurable count #1 register and simultaneously resets the internal counter to begin a new cycle of event accumulation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 146 register 0x510 : pmon c onfigurable count #2 bit type func tion default bit 15 r c2[15] x bit 14 r c2[14] x bit 13 r c2[13] x bit 12 r c2[12] x bit 11 r c2[11] x bit 10 r c2[10] x bit 9 r c2[9] x bit 8 r c2[8] x bit 7 r c2[7] x bit 6 r c2[6] x bit 5 r c2[5] x bit 4 r c2[4] x bit 3 r c2[3] x bit 2 r c2[2] x bit 1 r c2[1] x bit 0 r c2[0] x this register reports the number events, selected by the freedm-32a672 master performance monitor control register, that occurred in the previous accumulation interval. c2[15:0]: the c2[15:0] bits reports the number of selected events that have been detected since the last time this register was polled. this register is polled by writing to the freedm-32a672 master clock / bert activity monitor and accumulation trigger register. the write access transfers the internally accumulated error count to the configurable count #2 register and simultaneously resets the internal counter to begin a new cycle of event accumulation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 147 register 0x580 : rapi control bit type func tion default bit 15 r/w enable 0 bit 14 r/w staten 0 bit 13 r/w reserved 0 bit 12 to bit 4 unused xxxh bit 3 r/w all1enb 1 bit 2 r/w baddr[2] 1 bit 1 r/w baddr[1] 1 bit 0 r/w baddr[0] 1 this register provides the base address of the rx appi for purposes of responding to polling and device selection. this register also enables the rapi672. baddr[2:0]: the base address bits (baddr[2:0]) co nfigure the address space occupied by the freedm-32a672 device for purposes of responding to receive polling and receive device selection. during po lling, the baddr[2:0] bits are used to respond to polling via the rxaddr[2:0] pi ns. during device selection, the baddr[2:0] are used to select a freedm-32a672 device, enabling it to accept data on the receive appi. during data transfer, the rxdata[15:13] pins of the prepended c hannel address reflect the baddr[2:0] bits. all1enb: the all ones enable bit (all1enb) permits the freedm-32a672 to respond to receive polling and device selection when baddr[2:0] = ?111?. when all1enb is zero, the freedm-32a672 responds to receive polling and device selection when baddr[2:0] = rxaddr[2:0] = ?111?. when all1enb is one, the freedm-32a672 regards the all-ones address as a null address and does not respond to receive polling and device selection when baddr[2:0] = ?111?, regardless of the value of rxaddr[2:0].
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 148 reserved: the reserved bit must be set to zero for correct operation of the freedm- 32a672 device. staten: the rapi672 status enable bit (staten) enables the rapi672 to provide the status of an errored packet on rxdata[7:0] during transfer of the final word of that packet on the receive appi (reop and rerr high). when staten is set high, the rapi672 overwrites rxdata[7:0] of the final word of an errored packet with status information for that packet. when staten is set low, the rapi672 does not report detailed status information for an errored packet. the rxdata[15:0] connector description details the errored packet status reporting when staten is set high. enable: the rapi672 enable bit (enable) enables normal operation of the rapi672. when enable is set low, t he rapi672 will not transfer data from the rhdl672 into its internal fifos. when enable is set high, the rapi672 operates normally.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 149 register 0x600 : tapi control bit type func tion default bit 15 r/w enable 0 bit 14 r/w reserved 0 bit 13 r/w reserved 0 bit 12 to bit 4 unused xxxh bit 3 r/w all1enb 1 bit 2 r/w baddr[2] 1 bit 1 r/w baddr[1] 1 bit 0 r/w baddr[0] 1 this register provides the base address of the tx appi for purposes of responding to polling and tx appi data transfe rs. this register also enables the tapi672. baddr[2:0]: the base address bits (baddr[2:0]) co nfigure the address space occupied by the freedm-32a672 device for purposes of respondi ng to transmit polling and transmit data transfers. during polling, the txaddr[12:10] pins are compared with the baddr[2:0] bits to determine if the poll address identified by txaddr[9:0] is intended for a channel in this freedm-32a672 device. during data transmission, the txdata[15:13] pins of the prepended channel address are compared with the baddr[2:0] bits to determine if the data to follow is intended for this freedm-32a672 device. all1enb: the all ones enable bit (all1enb) permits the freedm-32a672 to respond to transmit polling and device selection when baddr[2:0] = ?111?. when all1enb is zero, the freedm-32a672 responds to transmit polling when baddr[2:0] = txaddr[12:10] = ?111? and device selection when baddr[2:0] = txdata[15:13] = ?111?. when all1enb is one, the freedm- 32a672 regards the all-ones address as a null address and does not respond to transmit polling and device selection when baddr[2:0] = ?111?, regardless of the values of txaddr[12:10] and txdata[15:13].
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 150 reserved: the reserved bits must be set to zero for correct operation of the freedm- 32a672 device. enable: the tapi672 enable bit (enable) enables normal operation of the tapi672. when enable is set low, the tapi672 will complete the current data transfer and will respond to any further transac tions on the tx appi normally (by setting trdy high), but data provided will be ignored. when enable is set high, the tapi672 operates normally.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 151 register 0x604 : tapi indirect channel provisioning bit type func tion default bit 15 r busy x bit 14 r/w rwb 0 bit 13 to bit 10 unused xh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 the indirect channel provisioning register provides the channel number used to access the tapi672 channel provisioning ram. writing to this register triggers an indirect channel register access. chan[9:0]: the indirect channel number bits (chan[9:0]) indicate the channel to be configured or interrogated in the indirect access. rwb: the read/write bar (rwb) bit selects between a provisioning/unprovisioning operation (write) or a query operation (read). writing a logic 0 to rwb triggers the provisioning or unprovisioning of the channel specified by chan[9:0]. writing a logic 1 to rwb triggers a query of the channel specified by chan[9:0].
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 152 busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available or to determine when a new indirect write operation may commence.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 153 register 0x608 : tapi indirect channel data register bit type func tion default bit 15 r/w prov 0 bit 14 to bit 8 unused xh bit 7 r/w blen[7] 0 bit 6 r/w blen[6] 0 bit 5 r/w blen[5] 0 bit 4 r/w blen[4] 0 bit 3 r/w blen[3] 0 bit 2 r/w blen[2] 0 bit 1 r/w blen[1] 0 bit 0 r/w blen[0] 0 the tapi indirect channel data register contains data read from the tapi672 channel provision ram after an indirect read operation or data to be written to channel provision ram in an indirect write operation. blen[7:0]: the channel burst length (blen[7:0]) bits report the data transfer burst length read from the tapi672 channel provision ram after an indirect read operation has completed. the data transfer burst length specifies the length (in bytes, less one) of burst data transfers on the transmit appi which are not terminated by the assertion of teop. the data transfer burst length can be specified on a per-channel basis. the data transfer burst length to be written to the channel provision ram in an indirect write operation must be set up in this register before triggering the write. blen[7:0] reflects the value written until the completion of a subsequent indirect read operation. prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from the tapi672 channel provision ram after an indirect read operation has completed. the provision enable flag to be written to the tapi672 channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when prov is set high, the
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 154 channel as indicated by chan[9:0] is provisioned. when prov is set low, the channel indicated by chan[9:0] is unprovisioned. prov reflects the value written until the completion of a subsequent indirect read operation.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 155 10 test features description the freedm-32a672 also supports a standard ieee 1149.1 five signal jtag boundary scan test port for use in board testing. all device inputs may be read and all device outputs may be forced via the jtag test port. 10.1 test mode registers test mode registers are used to apply test vectors during production testing of the freedm-32a672. production testing is enabled by asserting the pmctest pin. during production tests, freedm-32a672 registers are selected by the ta[12:0] pins. the address of a register on ta[12:0] is identical to the offset of that register when production testing is disabled (pmctest low). read accesses are enabled by asserting trdb low while write accesses are enabled by asserting twrb low. test mode register data is conveyed on the tdat[15:0] pins. test mode registers (as opposed to normal mode registers) are selected when ta[12]/trs is set high.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 156 table 17 ? test mode register memory map address ta[12:0] register 0x0000 - 0x07fe normal mode registers 0x0800 - 0x10fe reserved 0x1100 - 0x11fe rcas672 test registers 0x1200 - 0x123e rhdl672 test registers 0x1240 - 0x137e reserved 0x1380 - 0x13be thdl672 test registers 0x13c0 - 0x13fe reserved 0x1400 - 0x14fe tcas672 test registers 0x1500 - 0x151e pmon test registers 0x1520 - 0x157e reserved 0x1580 - 0x15be rapi672 test registers 0x15c0 - 0x15fe reserved 0x1600 - 0x163e tapi672 test registers 0x1640 - 0x1ffe reserved notes on test mode register bits: 1. writing values into unused register bits has no effect. however, to ensure software compatibility with future, feature-enhanced ve rsions of the pro duct, unused register bits must be written with logic zero. reading back unused bits can produce either a logic one or a logic zero; hence unused register bits should be masked off by software when read. 2. writable test mode register bits are not initialized upon reset unless otherwise noted. 10.2 jtag test port the freedm-32a672 jtag test access port (tap) allows access to the tap controller and the 4 tap registers: instruction, bypass, device identification and boundary scan. using the tap, device input logic levels can be read, device outputs can be forced, the device can be identified and the device scan path can be bypassed. for more details on the jtag port, please refer to the operations section.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 157 table 18 ? instruction register length - 3 bits instructions selected register instruction code ir[2:0] extest boundary scan 000 idcode identification 001 sample boundary scan 010 bypass bypass 011 bypass bypass 100 stctest boundary scan 101 bypass bypass 110 bypass bypass 111 10.2.1 identification register length - 32 bits version number - 2h part number - 7381h manufacturer's identification code - 0cdh device identification - 273810cdh 10.2.2 boundary scan register the boundary scan register is made up of 365 boundary scan cells, divided into input observation (in_cell), output (out_cell), and bi-directional (io_cell) cells. these cells are detailed in the following pages. the first 32 cells form the id code register, and carry the code 273810cdh. the cells are arranged as follows: table 19 ? boundary scan chain pin/ enable register bit cell type device i.d. rbclk_oen 0 out_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 158 pin/ enable register bit cell type device i.d. rbclk 1 out_cell - rbd_oen 2 out_cell - rbd 3 out_cell - tmv8dc 4 in_cell - tfp8b 5 in_cell - tmv8fpc 6 in_cell - tfpb[0] 7 in_cell - tmvck[0] 8 in_cell - td_oen[0] 9 out_cell - td[0] 10 out_cell - tclk[0] 11 in_cell - td_oen[1] 12 out_cell - td[1] 13 out_cell - tclk[1] 14 in_cell - td_oen[2] 15 out_cell - td[2] 16 out_cell - tclk[2] 17 in_cell - td_oen[3] 18 out_cell - td[3] 19 out_cell - tclk[3] 20 in_cell - td_oen[4] 21 out_cell - td[4] 22 out_cell - tclk[4] 23 in_cell - td_oen[5] 24 out_cell - td[5] 25 out_cell - tclk[5] 26 in_cell - td_oen[6] 27 out_cell - td[6] 28 out_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 159 pin/ enable register bit cell type device i.d. tclk[6] 29 in_cell - td_oen[7] 30 out_cell - td[7] 31 out_cell - tclk[7] 32 in_cell - tfpb[1] 33 in_cell - tmvck[1] 34 in_cell - td_oen[8] 35 out_cell - td[8] 36 out_cell - tclk[8] 37 in_cell - td_oen[9] 38 out_cell - td[9] 39 out_cell - tclk[9] 40 in_cell - td_oen[10] 41 out_cell - td[10] 42 out_cell - tclk[10] 43 in_cell - td_oen[11] 44 out_cell - td[11] 45 out_cell - tclk[11] 46 in_cell - td_oen[12] 47 out_cell - td[12] 48 out_cell - tclk[12] 49 in_cell - td_oen[13] 50 out_cell - td[13] 51 out_cell - tclk[13] 52 in_cell - td_oen[14] 53 out_cell - td[14] 54 out_cell - tclk[14] 55 in_cell - td_oen[15] 56 out_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 160 pin/ enable register bit cell type device i.d. td[15] 57 out_cell - tclk[15] 58 in_cell - tfpb[2] 59 in_cell - tmvck[2] 60 in_cell - td_oen[16] 61 out_cell - td[16] 62 io_cell - tclk[16] 63 in_cell - td_oen[17] 64 out_cell - td[17] 65 io_cell - tclk[17] 66 in_cell - td_oen[18] 67 out_cell - td[18] 68 io_cell - tclk[18] 69 in_cell - td_oen[19] 70 out_cell - td[19] 71 io_cell - tclk[19] 72 in_cell - td_oen[20] 73 out_cell - td[20] 74 io_cell - tclk[20] 75 in_cell - td_oen[21] 76 out_cell - td[21] 77 io_cell - tclk[21] 78 in_cell - td_oen[22] 79 out_cell - td[22] 80 io_cell - tclk[22] 81 in_cell - td_oen[23] 82 out_cell - td[23] 83 io_cell - tclk[23] 84 in_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 161 pin/ enable register bit cell type device i.d. tfpb[3] 85 in_cell - tmvck[3] 86 in_cell - td_oen[24] 87 out_cell - td[24] 88 io_cell - tclk[24] 89 in_cell - td_oen[25] 90 out_cell - td[25] 91 io_cell - tclk[25] 92 in_cell - td_oen[26] 93 out_cell - td[26] 94 io_cell - tclk[26] 95 in_cell - td_oen[27] 96 out_cell - td[27] 97 io_cell - tclk[27] 98 in_cell - td_oen[28] 99 out_cell - td[28] 100 io_cell - tclk[28] 101 in_cell - td_oen[29] 102 out_cell - td[29] 103 io_cell - tclk[29] 104 in_cell - td_oen[30] 105 out_cell - td[30] 106 io_cell - tclk[30] 107 in_cell - td_oen[31] 108 out_cell - td[31] 109 io_cell - tclk[31] 110 in_cell - tbd 111 in_cell - tbclk_oen 112 out_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 162 pin/ enable register bit cell type device i.d. tbclk 113 out_cell - pmctest 114 in_cell - rxaddr[0] 115 in_cell - rxaddr[1] 116 in_cell - rxaddr[2] 117 in_cell - rxclk 118 in_cell - rxdata_oen[0] 119 out_cell - rxdata[0] 120 io_cell - rxdata_oen[1] 121 out_cell - rxdata[1] 122 io_cell - rxdata_oen[2] 123 out_cell - rxdata[2] 124 io_cell - rxdata_oen[3] 125 out_cell - rxdata[3] 126 io_cell - rxdata_oen[4] 127 out_cell - rxdata[4] 128 io_cell - rxdata_oen[5] 129 out_cell - rxdata[5] 130 io_cell - rxdata_oen[6] 131 out_cell - rxdata[6] 132 io_cell - rxdata_oen[7] 133 out_cell - rxdata[7] 134 io_cell - rsx_oen 135 out_cell - rsx 136 io_cell - rxdata_oen[8] 137 out_cell - rxdata[8] 138 io_cell - rxdata_oen[9] 139 out_cell - rxdata[9] 140 io_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 163 pin/ enable register bit cell type device i.d. rxdata_oen[10] 141 out_cell - rxdata[10] 142 io_cell - rxdata_oen[11] 143 out_cell - rxdata[11] 144 io_cell - rxdata_oen[12] 145 out_cell - rxdata[12] 146 io_cell - rxdata_oen[13] 147 out_cell - rxdata[13] 148 io_cell - rxdata_oen[14] 149 out_cell - rxdata[14] 150 io_cell - rxdata_oen[15] 151 out_cell - rxdata[15] 152 io_cell - rxprty_oen 153 out_cell - rxprty 154 io_cell - rerr_oen 155 out_cell - rerr 156 io_cell - rmod_oen 157 out_cell - rmod 158 io_cell - reop_oen 159 out_cell - reop 160 io_cell - renb 161 in_cell - rpa_oen 162 out_cell - rpa 163 io_cell - rval_oen 164 out_cell - rval 165 io_cell - trdy_oen 166 out_cell - trdy 167 io_cell - terr_oen 168 out_cell
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 164 pin/ enable register bit cell type device i.d. terr 169 io_cell - tmod_oen 170 out_cell - tmod 171 io_cell - teop_oen 172 out_cell - teop 173 io_cell - txdata_oen[0] 174 out_cell - txdata[0] 175 io_cell - txdata_oen[1] 176 out_cell - txdata[1] 177 io_cell - txdata_oen[2] 178 out_cell - txdata[2] 179 io_cell - txdata_oen[3] 180 out_cell - txdata[3] 181 io_cell - txdata_oen[4] 182 out_cell - txdata[4] 183 io_cell - txdata_oen[5] 184 out_cell - txdata[5] 185 io_cell - txdata_oen[6] 186 out_cell - txdata[6] 187 io_cell - txdata_oen[7] 188 out_cell - txdata[7] 189 io_cell - tsx 190 in_cell - txprty_oen 191 out_cell - txprty 192 io_cell - txdata_oen[8] 193 out_cell - txdata[8] 194 io_cell - txdata_oen[9] 195 out_cell - txdata[9] 196 io_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 165 pin/ enable register bit cell type device i.d. txdata_oen[10] 197 out_cell - txdata[10] 198 io_cell - txdata_oen[11] 199 out_cell - txdata[11] 200 io_cell - txdata_oen[12] 201 out_cell - txdata[12] 202 io_cell - txdata_oen[13] 203 out_cell - txdata[13] 204 io_cell - txdata_oen[14] 205 out_cell - txdata[14] 206 io_cell - txdata_oen[15] 207 out_cell - txdata[15] 208 io_cell - unconnected 209 out_cell - unconnected 210 io_cell - txclk 211 in_cell - txaddr[0] 212 in_cell - txaddr[1] 213 in_cell - txaddr[2] 214 in_cell - unconnected 215 out_cell - unconnected 216 out_cell - txaddr[3] 217 in_cell - txaddr_oen[4] 218 out_cell - txaddr[4] 219 io_cell - txaddr[5] 220 in_cell - txaddr[6] 221 in_cell - txaddr[7] 222 in_cell - txaddr[8] 223 in_cell - txaddr[9] 224 in_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 166 pin/ enable register bit cell type device i.d. txaddr[10] 225 in_cell - txaddr[11] 226 in_cell - txaddr[12] 227 in_cell - tpa1_oen[0] 228 out_cell - tpa1[0] 229 io_cell - tpa1_oen[1] 230 out_cell - tpa1[1] 231 io_cell - tpa1_oen[2] 232 out_cell - tpa1[2] 233 io_cell - tpa2_oen[0] 234 out_cell - tpa2[0] 235 io_cell - tpa2_oen[1] 236 out_cell - tpa2[1] 237 io_cell - tpa2_oen[2] 238 out_cell - tpa2[2] 239 io_cell - d_oen[0] 240 out_cell - d[0] 241 io_cell - d_oen[1] 242 out_cell - d[1] 243 io_cell - d_oen[2] 244 out_cell - d[2] 245 io_cell - d_oen[3] 246 out_cell - d[3] 247 io_cell - d_oen[4] 248 out_cell - d[4] 249 io_cell - d_oen[5] 250 out_cell - d[5] 251 io_cell - d_oen[6] 252 out_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 167 pin/ enable register bit cell type device i.d. d[6] 253 io_cell - d_oen[7] 254 out_cell - d[7] 255 io_cell - d_oen[8] 256 out_cell - d[8] 257 io_cell - d_oen[9] 258 out_cell - d[9] 259 io_cell - d_oen[10] 260 out_cell - d[10] 261 io_cell - d_oen[11] 262 out_cell - d[11] 263 io_cell - d_oen[12] 264 out_cell - d[12] 265 io_cell - d_oen[13] 266 out_cell - d[13] 267 io_cell - d_oen[14] 268 out_cell - d[14] 269 io_cell - d_oen[15] 270 out_cell - d[15] 271 io_cell - a[2] 272 in_cell - a[3] 273 in_cell - a[4] 274 in_cell - a[5] 275 in_cell - a[6] 276 in_cell - a[7] 277 in_cell - a[8] 278 in_cell - a[9] 279 in_cell - a[10] 280 in_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 168 pin/ enable register bit cell type device i.d. a[11] 281 in_cell - ale 282 in_cell - wrb 283 in_cell - rdb 284 in_cell - csb 285 in_cell - intb_oen 286 out_cell - intb 287 out_cell - rclk[31] 288 in_cell - rd[31] 289 in_cell - rclk[30] 290 in_cell - rd[30] 291 in_cell - rclk[29] 292 in_cell - rd[29] 293 in_cell - rclk[28] 294 in_cell - rd[28] 295 in_cell - rclk[27] 296 in_cell - rd[27] 297 in_cell - rclk[26] 298 in_cell - rd[26] 299 in_cell - rclk[25] 300 in_cell - rd[25] 301 in_cell - rclk[24] 302 in_cell - rd[24] 303 in_cell - rmvck[3] 304 in_cell - rfpb[3] 305 in_cell - rclk[23] 306 in_cell - rd[23] 307 in_cell - rclk[22] 308 in_cell -
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 169 pin/ enable register bit cell type device i.d. rd[22] 309 in_cell - rclk[21] 310 in_cell - rd[21] 311 in_cell - rclk[20] 312 in_cell - rd[20] 313 in_cell - rclk[19] 314 in_cell - rd[19] 315 in_cell - rclk[18] 316 in_cell - rd[18] 317 in_cell - rclk[17] 318 in_cell - rd[17] 319 in_cell - rclk[16] 320 in_cell - rd[16] 321 in_cell - rmvck[2] 322 in_cell - rfpb[2] 323 in_cell - rclk[15] 324 in_cell - rd[15] 325 in_cell - rstb 326 in_cell - rclk[14] 327 in_cell - rd[14] 328 in_cell - rclk[13] 329 in_cell - rd[13] 330 in_cell - rclk[12] 331 in_cell - rd[12] 332 in_cell - rclk[11] 333 in_cell 1 rd[11] 334 in_cell 0 rclk[10] 335 in_cell 1 rd[10] 336 in_cell 1
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 170 pin/ enable register bit cell type device i.d. rclk[9] 337 in_cell 0 rd[9] 338 in_cell 0 rclk[8] 339 in_cell 1 rd[8] 340 in_cell 1 rmvck[1] 341 in_cell 0 rfpb[1] 342 in_cell 0 rclk[7] 343 in_cell 0 rd[7] 344 in_cell 0 rclk[6] 345 in_cell 1 rd[6] 346 in_cell 0 sysclk 347 in_cell 0 rclk[5] 348 in_cell 0 rd[5] 349 in_cell 0 rclk[4] 350 in_cell 0 rd[4] 351 in_cell 0 rclk[3] 352 in_cell 1 rd[3] 353 in_cell 1 rclk[2] 354 in_cell 1 rd[2] 355 in_cell 0 rclk[1] 356 in_cell 0 rd[1] 357 in_cell 1 rclk[0] 358 in_cell 1 rd[0] 359 in_cell 1 rmvck[0] 360 in_cell 0 rfpb[0] 361 in_cell 0 rmv8fpc 362 in_cell 1 rfp8b 363 in_cell 0 rmv8dc 364 in_cell 0
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 171 pin/ enable register bit cell type device i.d. tdo tap output - tdi tap input - tck tap clock - tms tap input - trstb tap input - notes: 1. rmv8dc is the first bit of the scan chain (closest to tdi). 2. enable cell pinname_oen, tristates pin pinname when set high. 3. cells titled ?unconnected? are output or bi-directional cells whose pad is unconnected to the device package. in the case of bi-directional cells, the pad always drives (i.e. never tri-states) and the pad input is the same logic value as the pad output. figure 6 ? input observation cell (in_cell) input pad d c clock-dr scan chain out input to internal logic shift-dr scan chain in 1 2 mux 1 2 1 2 1 2 i.d. code bit idcode g1 g2 in this diagram and those that follow, clock-dr is equal to tck when the current controller state is shift-dr or capture-dr, and unchanging otherwise. the multiplexor in the center of the diagram selects one of four
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 172 inputs, depending on the status of select lines g1 and g2. the id code bit is as listed in the table above. figure 7 ? output cell (out_cell) d c d c g1 g2 12 mux g1 1 1 mux output or enable from system logic scan chain in scan chain out extest output or enable shift-dr clock-dr update-dr 12 12 12 idcode i.d. code bit
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 173 figure 8 ? bi-directional cell (io_cell) d c d c g1 1 1 mux output from internal logic scan chain in scan chain out extest output to pin shift-dr clock-dr update-dr input from pin input to internal logic g1 1 2 mux 1 2 1 2 1 2 g2 idcode i.d. code bit
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 174 figure 9 ? layout of output en able and bi-directional cells output enable from internal logic (0 = drive) out_cell scan chain out scan chain in input to internal logic output from internal logic i/o pad io_cell scan chain in scan chain out
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 175 11 operations this section presents connection details to the pm4388 toctl device, and operating details for the jtag boundary scan feature. 11.1 toctl connections the required connections between the pm4388 toctl and the freedm- 32a672 are shown in the following table: table 20 ? freedm?toctl connections freedm pin direction toctl pin rclk[n] iclk/isig[m] rd[n] id[m] n.c. ifp[m] tclk[n] efp/rclk/esig[m] td[n] ed[m] all 8 framers in the toctl should be programmed to operate in ?clock master: nxds0? mode in both the ingress and egress direction. 11.2 jtag support the freedm-32a672 supports the ieee boundary scan specification as described in the ieee 1149.1 standards. the test access port (tap) consists of the five standard pins, trstb, tck, tms, tdi and tdo used to control the tap controller and the boundary scan registers. the trstb input is the active low reset signal used to reset the tap controller. tck is the test clock used to sample data on input, tdi and to output data on output, tdo. the tms input is used to direct the tap controller through its states. the basic boundary scan architecture is shown below.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 176 figure 10 ? boundary scan architecture boundary scan register control tdi tdo device identification register bypass register instruction register and decode trstb tms tck test access port controller mux dff select tri-state enable the boundary scan architecture consists of a tap controller, an instruction register with instruction decode, a bypass register, a device identification register and a boundary scan register. the tap controller interprets the tms input and generates control signals to load the instruction and data registers. the instruction register with instruction decode block is used to select the test to be executed and/or the register to be accessed. the bypass register offers a single bit delay from primary input, tdi to primary output , tdo. the device identification register contains the device identification code. the boundary scan register allows testing of board inter-connectivity. the boundary scan register consists of a shift register placed in series with device inputs and outputs. using the boundary scan register, all digital inputs can be
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 177 sampled and shifted out on primary output tdo. in addition, patterns can be shifted in on primary input, tdi and forced onto all digital outputs. tap controller the tap controller is a synchronous finite state machine clocked by the rising edge of primary input, tck. all state transitions are controlled using primary input, tms. the finite state machine is described below.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 178 figure 11 ? tap controller finite state machine test-logic-reset run-test-idle select-dr-scan select-ir-scan capture-dr capture-ir shift-dr shift-ir exit1-dr exit1-ir pause-dr pause-ir exit2-dr exit2-ir update-dr update-ir trstb=0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0 0 1 1 1 1 1 1 all transitions dependent on input tms 0 0 0 0 0 1
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 179 test-logic-reset the test logic reset state is used to disable the tap logic when the device is in normal mode operation. the state is entered asynchronously by asserting input, trstb. the state is entered synchronously regardless of the current tap controller state by forcing input, tms high for 5 tck clock cycles. while in this state, the instruction register is set to the idcode instruction. run-test-idle the run test/idle state is used to execute tests. capture-dr the capture data register state is used to load parallel data into the test data registers selected by the current instruction. if the selected register does not allow parallel loads or no loading is required by the current instruction, the test register maintains its value. loading occurs on the rising edge of tck. shift-dr the shift data register state is used to shift the selected test data registers by one stage. shifting is from msb to lsb and occurs on the rising edge of tck. update-dr the update data register state is used to load a test register's parallel output latch. in general, the output latches are used to control the device. for example, for the extest instruction, the boundary scan test register's parallel output latches are used to control the device's outputs. the parallel output latches are updated on the falling edge of tck. capture-ir the capture instruction register state is used to load the instruction register with a fixed instruction. the load occurs on the rising edge of tck. shift-ir the shift instruction register state is used to shift both the instruction register and the selected test data registers by one stage. shifting is from msb to lsb and occurs on the rising edge of tck.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 180 update-ir the update instruction register state is used to load a new instruction into the instruction register. the new instruction must be scanned in using the shift-ir state. the load occurs on the falling edge of tck. the pause-dr and pause-ir states are provided to allow shifting through the test data and/or instruction registers to be momentarily paused. boundary scan instructions the following is a description of the standard instructions. each instruction selects a serial test data register path between input, tdi and output, tdo. bypass the bypass instruction shifts data from input, tdi to output, tdo with one tck clock period delay. the instruction is used to bypass the device. extest the external test instruction allows testing of the interconnection to other devices. when the current instruction is the extest instruction, the boundary scan register is place between input, tdi and output, tdo. primary device inputs can be sampled by loading the boundary scan register using the capture-dr state. the sampled values can then be viewed by shifting the boundary scan register using the shift-dr state. primary device outputs can be controlled by loading patterns shifted in through input tdi into the boundary scan register using the update-dr state. sample the sample instruction samples all the device inputs and outputs. for this instruction, the boundary scan register is placed between tdi and tdo. primary device inputs and outputs can be sampled by loading the boundary scan register using the capture-dr state. the sampled values can then be viewed by shifting the boundary scan register using the shift-dr state. idcode the identification instruction is used to connect the identification register between tdi and tdo. the device's identification code can then be shifted out using the shift-dr state.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 181 stctest the single transport chain instruction is used to test out the tap controller and the boundary scan register during production test. when this instruction is the current instruction, the boundary scan register is connected between tdi and tdo. during the capture-dr state, the device identification code is loaded into the boundary scan register. the code can then be shifted out output, tdo using the shift-dr state. intest the internal test instruction is used to exercise the device's internal core logic. when this instruction is the current instruction, the boundary scan register is connected between tdi and tdo. during the update-dr state, patterns shifted in on input, tdi are used to drive primary inputs. during the capture-dr state, primary outputs are sampled and loaded into the boundary scan register.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 182 12 functional timing 12.1 receive h-mvip link timing the timing relationship of the receive data clock (rmv8dc), frame pulse clock (rmv8fpc), data (rd[n]) and frame pulse (rfp8b) signals of a link configured for 8.192 mbps h-mvip operation with a type 0 frame pulse is shown in figure 12. the falling edges of each rmv8fpc are aligned to a falling edge of the corresponding rmv8dc for 8.192 mbps h-mvip operation. the freedm- 32a672 samples rfp8b low on the falling edge of rmv8fpc and references this point as the start of the next frame. the freedm-32a672 samples the data provided on rd[n] at the ? point of the data bit using the rising edge of rmv8dc as indicated for bit 1 (b1) of time-slot 0 (ts 0) in figure 12. b1 is the most significant bit and b8 is the least significant bit of each octet. time-slots can be ignored by setting the prov bit in the corresponding word of the receive channel provision ram in the rcas672 block to low. figure 12 ? receive 8.192 mbps h-mvip link timing rmv8dc (16 mhz) rfp8b rd[n] b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 ts 127 ts 0 ts 1 rmv8fpc (4 mhz) the timing relationship of the receive data clock (rmvck[n]), data (rd[m], where 8n m 8n+7) and frame pulse (rfpb[n]) signals of a link configured for 2.048 mbps h-mvip operation with a type 0 frame pulse is shown in figure 13. the freedm-32a672 samples rfpb[n] low on t he falling edge of the corresponding rmvck[n] and references this point as the start of the next frame. the freedm-32a672 samples the data provided on rd[m] at the ? point of the data bit using the rising edge of the corresponding rmvck[n] as indicated for bit 1 (b1) of time-slot 0 (ts 0) in figure 13. b1 is the most significant bit and b8 is the least significant bit of each octet. time-slots can be ignored by setting the prov bit in the corresponding word of the receive channel provision ram in the rcas672 block to low.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 183 figure 13 ? receive 2.048 mbps h-mvip link timing rfpb[n] rd[m] b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 ts 31 ts 0 ts 1 rmvck[n] (4 mhz) 12.2 transmit h-mvip link timing the timing relationship of the transmit data clock (tmv8dc), frame pulse clock (tmv8fpc), data (td[n]) and frame pulse (tfp8b) signals of a link configured for 8.192 mbps h-mvip operation with a type 0 frame pulse is shown in figure 14. the falling edges of each tmv8fpc are aligned to a falling edge of the corresponding tmv8dc for 8.192 mbps h-mvip operation. the freedm- 32a672 samples tfp8b low on the falling edge of tmv8fpc and references this point as the start of the next frame. the freedm-32a672 updates the data provided on td[n] on every second falling edg e of tmv8dc as indicated for bit 2 (b2) of time-slot 0 (ts 0) in figure 14. the first bit of the next frame is updated on td[n] on the falling tmv8dc clock edge for which tfp8b is also sampled low. b1 is the most significant bit and b8 is the least significant bit of each octet. time-slots that are not provisioned to belong to any channel (prov bit in the corresponding word of the transmit channel provision ram in the tcas672 block set low) transmits the contents of the idle fill time-slot data register. figure 14 ? transmit 8.192 mbps h-mvip link timing tmv8dc (16 mhz) tfp8b td[n] b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 ts 127 ts 0 ts 1 tmv8fpc (4 mhz)
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 184 the timing relationship of the transmit data clock (tmvck[n]), data (td[m], where 8n m 8n+7) and frame pulse (tfpb[n]) signals of a link configured for 2.048 mbps h-mvip operation with a type 0 frame pulse is shown in figure 15. the freedm-32a672 samples tfpb[n] low on the falling edge of the corresponding tmvck[n] and references this point as the start of the next frame. the freedm-32a672 updates the data provided on td[m] on every second falling edge of the corresponding tmvck[n] as indicated for bit 2 (b2) of time-slot 0 (ts 0) in figure 15. the first bit of the next frame is updated on td[m] on the falling tmvck[n] clock edge for which tfpb[n] is also sampled low. b1 is the most significant bit and b8 is the least significant bit of each octet. time-slots that are not provisioned to belong to any channel (prov bit in the corresponding word of the transmit channel provision ram in the tcas672 block set low) transmits the contents of the idle fill time-slot data register. figure 15 ? transmit 2.048 mbps h-mvip link timing tfpb[n] td[m] b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 ts 31 ts 0 ts 1 tmvck[n] (4 mhz) 12.3 receive non h-mvip link timing the timing relationship of the receive clock (rclk[n]) and data (rd[n]) signals of an unchannelised link is shown in figure 16. the receive data is viewed as a contiguous serial stream. there is no concept of time-slots in an unchannelised link. every eight bits are grouped together into a byte with arbitrary alignment. the first bit received (b1 in figure 16) is deemed the most significant bit of an octet. the last bit received (b8) is deemed the least significant bit. bits that are to be processed by the freedm-32a672 are clocked in on the rising edge of rclk[n]. bits that should be ignored (x in figure 16) are squelched by holding rclk[n] quiescent. in figure 16, the quiescent period is shown to be a low level on rclk[n]. a high level, effected by extending the high phase of the previous valid bit, is also acceptable. selection of bits for processing is arbitrary and is not subject to any byte alignment nor frame boundary considerations.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 185 figure 16 ? unchannelised receive link timing rclk[n] rd[n] b1 b2 b3 b4 x b5 x x x b6 b7 b8 b1 x the timing relationship of the receive clock (rclk[n]) and data (rd[n]) signals of a channelised t1/j1 link is shown in figure 17. the receive data stream is a t1/j1 frame with a single framing bit (f in figure 17) followed by octet bound time-slots 1 to 24. rclk[n] is held quiescent during the framing bit. the rd[n] data bit (b1 of ts1) clocked in by the first rising edge of rclk[n] after the framing bit is the most significant bit of time-slot 1. the rd[n] bit (b8 of ts24) clocked in by the last rising edge of rclk[n] before the framing bit is the least significant bit of time-slot 24. in figure 17, the quiescent period is shown to be a low level on rclk[n]. a high level, effected by extending the high phase of bit b8 of time-slot ts24, is equally acceptable. in channelised t1/j1 mode, rclk[n] can only be gapped during the framing bit. it must be active continuously at 1.544 mhz during all time-slot bits. time-slots can be ignored by setting the prov bit in the corresponding word of the receive channel provision ram in the rcas672 block to low. figure 17 ? channelised t1/j1 receive link timing rclk[n] rd[n] b7b8 f b1b2b3b4b5b6b7b8b1b2b3 ts 24 ts 1 ts 2 the timing relationship of the receive clock (rclk[n]) and data (rd[n]) signals of a channelised e1 link is shown in figure 18. the receive data stream is an e1 frame with a singe framing byte (f1 to f8 in figure 18) followed by octet bound time-slots 1 to 31. rclk[n] is held quiescent during the framing byte. the rd[n] data bit (b1 of ts1) clocked in by the first rising edge of rclk[n] after the framing byte is the most significant bit of time-slot 1. the rd[n] bit (b8 of ts31) clocked in by the last rising edge of rlclk[n] before the framing byte is the least significant bit of time-slot 31. in figure 18, the quiescent period is shown to be a low level on rclk[n]. a high level, effected by extending the high phase of bit b8 of time-slot ts31, is equally acceptable. in channelised e1 mode, rclk[n] can only be gapped during the framing byte. it must be active continuously at 2.048 mhz during all time-slot bits. time-slots can be ignored by setting the
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 186 prov bit in the corresponding word of the receive channel provision ram in the rcas672 block to low. figure 18 ? channelised e1 receive link timing rclk[n] rd[n] b6 b7 f1 f2 f3 f4 f5 f6 f7 f8 b1 b2 b3 ts 31 fas / nfas ts 1 b8 b4 b5 b6 b7 b8 b1 b2 b3 b4 ts 2 12.4 transmit non h-mvip link timing the timing relationship of the transmit clock (tclk[n]) and data (td[n]) signals of a unchannelised link is shown in figure 19. the transmit data is viewed as a contiguous serial stream. there is no concept of time-slots in an unchannelised link. every eight bits are grouped together into a byte with arbitrary byte alignment. octet data is transmitted from most significant bit (b1 in figure 19) and ending with the least significant bit (b8 in figure 19). bits are updated on the falling edge of tclk[n]. a transmit link may be stalled by holding the corresponding tclk[n] quiescent. in figure 19, bits b5 and b2 are shown to be stalled for one cycle while bit b6 is shown to be stalled for three cycles. in figure 19, the quiescent period is shown to be a low level on tclk[n]. a high level, effected by extending the high phase of the previous valid bit, is also acceptable. gapping of tclk[n] can occur arbitrarily without regard to byte nor frame boundaries. figure 19 ? unchannelised transmit link timing tclk[n] td[n] b1 b2 b3 b4 b5 b6 b7 b8 b1 b2 the timing relationship of the transmit clock (tclk[n]) and data (td[n]) signals of a channelised t1/j1 link is shown in figure 20. the transmit data stream is a t1/j1 frame with a single framing bit (f in figure 20) followed by octet bound time-slots 1 to 24. tclk[n] is held quiescent during the framing bit. the most significant bit of each time-slot is transmitted first (b1 in figure 20). the least significant bit of each time-slot is transmitted last (b8 in figure 20). the td[n] bit (b8 of ts24) before the framing bit is the least significant bit of time-slot 24. in figure 20, the quiescent period is shown to be a low level on tclk[n]. a high
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 187 level, effected by extending the high phase of bit b8 of time-slot ts24, is equally acceptable. in channelised t1/j1 mode, tclk[n] can only be gapped during the framing bit. it must be active continuously at 1.544 mhz during all time-slot bits. time-slots that are not provisioned to belong to any channel (prov bit in the corresponding word of the transmit channel provision ram in the tcas672 block set low) transmit the contents of the idle fill time-slot data register. figure 20 ? channelised t1/j1 transmit link timing tclk[n] td[n] b7 b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 b2 b3 ts 24 ts 1 ts 2 f the timing relationship of the transmit clock (tclk[n]) and data (td[n]) signals of a channelised e1 link is shown in figure 21. the transmit data stream is an e1 frame with a singe framing byte (fas/nfas in figure 21) followed by octet bound time-slots 1 to 31. tclk[n] is held quiescent during the framing byte. the most significant bit of each time-slot is transmitted first (b1 in figure 21). the least significant bit of each time-slot is transmitted last (b8 in figure 21). the td[n] bit (b8 of ts31) before the framing byte is the least significant bit of time-slot 31. in figure 21, the quiescent period is shown to be a low level on tclk[n]. a high level, effected by extending the high phase of bit b8 of time-slot 31, is equally acceptable. in channelised e1 mode, tclk[n] can only be gapped during the framing byte. it must be active continuously at 2.048 mhz during all time-slot bits. time-slots that are not provisioned to belong to any channel (prov bit in the corresponding word of the transmit channel provision ram in the tcas672 block set low) transmit the contents of the idle time-slot fill data register. figure 21 ? channelised e1 transmit link timing tclk[n] td[n] b6 b7 b1 b2 b3 ts 31 fas / nfas ts 1 b8 b4 b5 b6 b7 b8 b1 b2 b3 b4 ts 2 12.5 receive appi timing the receive any-phy packet interface (appi) timing is shown in figure 22 through figure 24. the freedm-32a672 device provides data to an external
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 188 controller using the receive appi. the following discussion surrounding the receive appi functional timing assumes that multiple freedm-32a672 devices share a single external controller. all rx appi signals are shared between the freedm-32a672 devices. figure 22 ? receive appi timing (normal transfer) dev 0 null dev 7 null dev 6 null dev 4 null dev 0 null dev 1 null dev 3 null dev 2 null dev 0 dev 7 dev 6 dev 4 dev 0 dev 1 dev 3 dev 2 ch 2 d0 d1 d2 d3 d4 d5 d6 d7 dev 0 dev 0 dev 0 dev 0 rxclk rxaddr[2:0] rpa renb rxdata[15:0] rval rsx reop rmod rerr figure 22 shows the transfer of an 8 word packet across the rx appi from freedm-32a672 device 0, channel 2. in this example, seven freedm-32a672 devices are sharing the rx appi, with device 5 being the null address. the data transfer begins when the external controller selects freedm-32a672 device 0 by placing that address on t he rxaddr[2:0] inputs and setting renb high. the external controller sets renb low in the next rxclk cycle to commence data transfer across the rx appi. the freedm-32a672 samples renb low and responds by asserting rsx two rxclk cycles later. the start of all burst data transfers is qualified with rsx and an in-band channel address on rxdata[15:0] to associate the data to follow with a hdlc channel. during the cycle when d2 is placed on rxdata[15:0], the external controller is unable to accept any further data and sets renb high. two rxclk cycles later, the freedm-32a672 tristates the rx appi. the external controller may hold renb high for an indeterminate number of rxclk cycles. the freedm- 32a672 will wait until the external contro ller returns renb low. because the freedm-32a672 does not support interrupted data transfers on the rx appi, the external controller must reselect freedm-32a672 device 0 or output a null address during the clock cycle before it returns renb low. however, while renb remains high, the address on the rxaddr[2:0] signals may change. when the freedm-32a672 device 0 samples renb low, it continues data transfer by providing d4 on rxdata[15:0]. note that if d3 were the final word of the packet (status), in response to sampling reop high, the external controller does not have to reselect freedm-32a672 device 0. this is shown in figure 25.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 189 the freedm-32a672 will not pause burst data transfers across the rx appi. the freedm-32a672 automatically deselects at the end of all burst data transfers. the freedm-32a672 must be re selected before any further data will be transferred across the rx appi. the rval and reop signals indicate the presence and end of valid packet data respectively. the rerr and rmod signals are only valid at the end of a packet and are qualified with the reop signal. when a packet is errored, the freedm- 32a672 may be programmed to overwrite rxdata[7:0] in the final word of packet transfer with status information indicating the cause of the error. rxdata[15:0] is not modified if a packet is error free. the rxaddr[2:0] signals serve to po ll freedm-32a672 devices as well as for selection. during data transfer, the rxaddr[2:0] signals continue to poll the freedm-32a672 devices sharing the rx appi. polled results are returned on the rpa signal. note that each poll address is separated by a null address to generate tristate turn-around cycle in order to prevent multiple freedm-32a672 devices from briefly driving rpa. if rpa is a point-to-point signal for each freedm-32a672 device on the board, then the tristate turn-around cycle is not required, thereby effectively doubling the polling bandwidth at the expense of extra signals. polled results reflect the status of the two fifos in the rapi672. polled responses always refer to the next data transfer. in other words, polled responses during or after the rxclk cycle where rsx is set high refer to the fifo which is not involved in the current data transfer. for example, once fifo one begins transferring data on the rx appi (rsx set high), any polls against that freedm-32a672 device respond with the status of fifo two. this allows the external controller to gather knowledge about the fifo not involved in the current data transfer so that it can anticipate reselecting that freedm-32a672 device (via renb) to maximize bandwidth on the rx appi (shown in figure 24). figure 23 ? receive appi timing (auto deselection) dev 0 null dev 7 null dev 6 null dev 4 null dev 0 null dev 3 null dev 2 null dev 0 dev 7 dev 4 dev 0 dev 3 dev 2 ch 2 d0 d1 d98 d99 ch 8 d0 d1 dev 0 dev 0 dev 0 dev 0 rxclk rxaddr[2:0] rpa renb rxdata[15:0] rval rsx reop rmod rerr
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 190 figure 23 shows the transfer of a 100 word packet across the rx appi from freedm-32a672 device 0, channel 2 followed by the transfer of a 2 word packet from freedm-32a672 device 0, channel 8. more importantly, figure 23 illustrates that, for back- to-back transfers from the same freedm-32a672 (device 0), it must be reselected before any further data is provided on the rx appi. at the end of the first 100 word packet transfer across the rx appi, the freedm-32a672 automatically deselects and must be reselected before the second two word packet is transferred. when the external controller samples reop high, it recognizes that the burst transfer has completed. two rxclk cycles later, the external controller reselects freedm-32a672 device 0 by setting renb high and placing address 0 on the rxaddr[2:0] signals. when the freedm-32a672 samples renb low, it begins the next data transfer as before. figure 24 ? receive appi timing (optimal reselection) dev 0 null dev 7 null dev 6 null null dev 0 null dev 4 null dev 3 null dev 0 dev 7 dev 0 dev 4 ch 2 d0 d1 d125 d126 d127 ch 2 d128 dev 0 dev 0 dev 0 dev 0 rxclk rxaddr[2:0] rpa renb rxdata[15:0] rval rsx reop rmod rerr figure 24 shows optimal bandwidth utilization across the rx appi. with knowledge that the maximum burst data transfer (excluding channel address prepend) is 256 bytes, i.e. 128 words, the external controller sets renb high when the 127 th word (d126) is placed on rxdata[15:0] in anticipation of the end of a burst transfer. the freedm-32a672 completes the burst data transfer and tristates the rx appi one rxclk cycle after renb is sampled high. because the burst data transfer is complete and renb is immediately returned low following selection, the freedm-32a672 immediately begins the next data transfer following the single turn-around cycle. the protocol dictates that at least one tristate turn-around cycle be inserted between data transfers, even if the external controller is reselecting the same freedm-32a672 device. in other words, figure 24 shows the earliest possible time that the external controller could have set renb high to reselect freedm- 32a672 device 0.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 191 figure 25 ? receive appi timing (boundary condition) dev 0 null dev 7 null dev 6 null dev 4 null dev 7 dev 1 null dev 3 null dev 2 null dev 0 dev 7 dev 6 dev 4 dev 7 dev 1 dev 3 dev 2 ch 2 d0 d1 d2 d3 ch 1 d8 d9 dev 7 dev 7 rxclk rxaddr[2:0] rpa renb rxdata[15:0] rval rsx reop rmod rerr figure 25 shows the boundary condition where a packet transfer completes shortly after the external controller has set renb high to pause the freedm- 32a672 device. the second data transfer is the final two words of a packet for freedm-32a672 device 7, channel 1. when freedm-32a672 device 0 places d2 on rxdata[15:0], the external controller sets renb high to pause the freedm-32a672 device. in the following rxclk cycle, the freedm-32a672 provides d3 on rxdata[15:0] and sets reop high to conclude packet transfer. the external controller samples reop high while renb is high and recognizes that the packet transfer is complete. the external controller now knows that it doesn?t need to reselect freedm-32a672 device 0, but can select another freedm-32a672 device sharing the rx appi. the external controller decides to select freedm-32a672 device 7 by placing this address on the rxaddr[2:0] signals. the external controller sets renb low to commence data transfer from freedm-32a672 device 7. 12.6 transmit appi timing the transmit any-phy packet interface (appi) timing is shown in figure 26. an external controller provides data to the freedm-32a672 device using the transmit appi. the following discussion surrounding the transmit appi functional timing assumes that multiple freedm-32a672 devices share a single external controller. the three most significant bits of txaddr[12:0] perform device selection for purposes of polling while the ten least significant bits provide the channel poll address. all tx appi signals are shared between the freedm- 32a672 devices.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 192 figure 26 ? transmit appi timing (normal transfer) ch 0 d0 d1 d2 d126 d127 ch 0 d128 d129 d130 d131 d132 d254 d255 dev 4 dev 4 txclk trdy txdata[15:0] tsx teop tmod terr figure 26 shows transfer of a 256 word packet on the tx appi of freedm- 32a672 device 4, channel 0. the maximum burst data transfer (excluding channel address prepend) is 128 words, so two data transfers are required to complete the transfer of the 256 word packet. the start of all burst data transfers is qualified with the tsx signal and an in-band channel address on txdata[15:0] to associate the data to follow with a hdlc channel. the teop signal indicates the end of valid packet data. the tmod and terr signals held low except at the end of a packet (teop set high). the freedm-32a672 starts driving the trdy signal one txclk cycle after tsx is sampled high. upon sampling the trdy signal high, the external controller completes the current burst data transfer. the freedm-32a672 tristates the trdy signal one txclk cycle after it has been driven high. this is the case for the first burst data transfer in figure 26. in the second burst data transfer, the freedm-32a672 drives the trdy signal low to indicate that the fifos in the tapi672 are full and no further data may be transferred. upon sampling the trdy signal low, the external controller must hold the last valid word of data on txdata[15:0]. the freedm-32a672 may drive trdy low for an indeterminate number of txclk cycles. during this time, the external controller must wait and is not permitted to begin another burst data transfer until trdy is sampled high. when the tapi672 has at least one empty fifo, the freedm-32a672 drives the trdy signal high. upon sampling the trdy signal high, the external controller completes the current burst data transfer. the freedm-32a672 tristates the trdy signal one txclk cycle after it has been driven high. the external controller must sample the trdy signal high before it can begin the next burst data transfer. this prevents the external controller from bombarding the freedm-32a672 device with small packets and allows the freedm- 32a672 to perform the necessary house-keeping and clean-up associated with the ending of burst data transfers. this protocol also ensures that transitions between burst data transfers do not require any extra per channel storage, thereby simplifying implementation of both the external controller and the freedm-32a672 device. figure 27 illustrates this condition.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 193 figure 27 ? transmit appi timing (special conditions) ch 0 d0 ch 671 d0 d1 d2 ch 2 d0 dev 5 dev 5 dev 3 dev 3 txclk trd y txdata[15:0] tsx teop tmod terr figure 27 shows two special conditions ? (1) the transfer of a one word packet illustrating how the external controller must wait until trdy has been sampled high before the next data transfer can begin, and (2) the transfer of a packet which completes when trdy is set low illustrating that although the packet has been completely transferred, t he external controller must still wait until trdy has been sampled high before the next data transfer can begin. the first data transfer is a single word packet for freedm-32a672 device 3, channel 0. the freedm-32a672 asserts trdy high one txclk cycle after tsx is sampled high. the tx appi protocol dictates that the external controller must wait until trdy is sampled high before beginning the next data transfer for freedm-32a672 device 5, channel 671. the external controller must hold the last valid word on txdata[15:0] until trdy is sampled high. in this case, that data is a don?t care. the freedm-32a672 tristates the trdy signal one txclk cycle after it has been driven high. the second transfer is a three word packet which completes transfer in the same txclk cycle that trdy is sampled low by the external controller. again, the external controller must hold the last valid word on txdata[15:0] until trdy is sampled high. in this case, that data is d2, the last word of the packet. the freedm-32a672 may drive trdy low for an indeterminate number of txclk cycles. during this time, the external controller must wait and is not permitted to begin another burst data transfer until trdy is sampled high. when the external controller samples trdy high, the current burst transfer is deemed to be complete and the external controller may begin the next data transfer. the freedm-32a672 tristates the trdy signal one txclk cycle after it has been driven high.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 194 figure 28 ? transmit appi timing (polling) ch 671 ch 0 ch 254 ch 8 null ch 0 ch 399 null ch 671 ch 0 ch 254 ch 8 ch 0 ch 0 ch 399 hungry starve hungry starve hungry starve starve ok uflow ok ok ok ok uflow ch 0 ch 1 ch 255 ch 9 ch 1 ch 1 ch 400 starve hungry starve hungry hungry hungry starve ok ok uflow ok ok ok uflow dev 1 dev 1 dev 0 dev 0 dev 1 dev 1 dev 0 dev 0 dev 1 dev 1 dev 0 dev 0 txclk txaddr[12:0] tpa1[0] tpa1[1] tpa1[2] tpa2[0] tpa2[1] tpa2[2] polling is completely decoupled from device and channel selection on the tx appi. accordingly, the txaddr[12:0] si gnals continue to provide only a poll address for any of the freedm-32a672 devices sharing the tx appi. the most significant three bits provide the device address and the least significant ten bits provide the channel address. poll results are returned on the tpan[2:0] signals. the tpan[0] bit indicates whether or not space exists in the channel fifo for data (high means space exists in the channel fifo) and the tpan[1] bit indicates whether or not that polled channel fifo is at risk of underflowing and should be provided data soon (high means the channel fifo is at risk of underflowing). the tpan[2] bit indicates whether or not an underflow condition has occurred on the polled channel fifo (high means an underflow condition occurred on that channel). in figure 28, channel 671 in device 0 reports that space does not exist for data in the channel fifo, that there is currently no risk of underflow on that channel (hungry) and that an underflow event has not occurred on this channel since the last poll. channel 0 in device 0 reports that space exists for data in the channel fifo, that there is currently a risk of underflow on that channel (starving) and that an underflow event has occurred on this channel since the last poll. polled results for two channels provide a two fold increase in the polling bandwidth on the tx appi to accommodate the high density of 672 channels. 12.7 bert interface the timing relationship between the receive link clock and data (rclk[n] / rd[n]) and the receive bert port signals (rbclk / rbd) is shown in figure 29. bert is not supported for h-mvip links. for non h-mvip links, the selected rclk[n] is placed on rbclk after an asynchronous delay. the selected receive link data (rd[n]) is sampled on the rising edge of the associated rclk[n] and transferred to rbd on the falling edge of rbclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 195 figure 29 ? receive bert port timing rclk[n] rd[n] b1 b2 b3 b4 x b5 x x x b6 b7 b8 b1 x rbclk rbd b1 b2 b3 b4 b5 b6 b7 b8 b1 the timing relationship between the transmit link clock and data (tclk[n] / td[n]) and the transmit bert port signals (tbclk / tbd) is shown in figure 30. bert is not supported for h-mvip links. tclk[n] is shown to have an arbitrary gapping. when tclk[n] is quiescent, tbd is ignored (x in figure 30). the selected tclk[n] is buffered and placed on tbclk. the transmit bert data (tbd) is sampled on the rising edge of the tbclk and transferred to the selected td[n] on the falling edge of tclk[n]. figure 30 ? transmit bert port timing tclk[n] tbd b1 b2 b3 b4 x b5 x x x b6 b7 b8 b1 x b2 tbclk td[n] b1 b2 b3 b4 b5 b6 b7 b8 b1
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 196 13 absolute maximum ratings maximum rating are the worst case limits that the device can withstand without sustaining permanent damage. they are not indicative of normal operating conditions. table 21 ? freedm-32a672 absolute maximum ratings case temperature under bias -40c to +85c storage temperature -40c to +125c supply voltage (+3.3 volt v dd3.3 ) -0.3v to +4.6v supply voltage (+2.5 volt v dd2.5 ) -0.3v to +3.5v voltage on any pin (non any-phy) -0.3v to +6.0v volatge on any pin (any-phy) -0.5v to v dd3.3 + 0.5v static discharge voltage 1000 v latch-up current 100 ma dc input current 20 ma lead temperature +230c absolute maximum junction temperature +150c
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 197 14 d.c. characteristics (t a = -40c to +85c, v dd3.3 = 3.0 v to 3.6 v, v dd2.5 = 2.3 v to 2.7v) table 22 ? freedm-32a672 d.c. characteristics symbol parameter min typ max units conditions v dd3.3 3.3v power supply 3.0 3.3 3.6 volts note 4. v dd2.5 2.5v power supply 2.3 2.5 2.7 volts note 4. v il any-phy input low voltage -0.5 0.6 volts v ih any-phy input high voltage 2.0 v dd3.3 + 0.5 volts v ol output or bi- directional low voltage 0.4 volts i ol = -4 ma for all outputs except rbclk, tbclk, rbd, d[15:0], intb, tpan[2:0], trdy, rpa, rsx, reop, rxdata[15:0], rxprty, rmod and rerr where i ol = -8 ma. note 3. v oh output or bi- directional high voltage 2.4 volts i oh = 4 ma for all outputs except rbclk, tbclk, rbd, d[15:0], intb, tpan[2:0], trdy, rpa, rsx, reop, rxdata[15:0], rxprty, rmod and rerr where i oh = 8 ma. note 3. v t+ schmitt triggered input high voltage 2.0 5.5 volts v t- schmitt triggered input low voltage -0.2 0.6 volts i ilpu input low current +10 45 +100 a v il = gnd, notes 1, 3, 4. i ihpu input high current -10 0 +10 a v ih = v dd , notes 1, 3.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 198 symbol parameter min typ max units conditions i il input low current -10 0 +10 a v il = gnd, notes 2, 3. i ih input high current -10 0 +10 a v ih = v dd , notes 2, 3. c in input capacitance 5 pf excludes package. package typically 2 pf. note 4. c out output capacitance 5 pf all pins. excludes package. package typically 2 pf. note 4. c io bi-directional capacitance 5 pf all pins. excludes package. package typically 2 pf. note 4. l pin pin inductance 2 nh all pins. note 4. i ddop operating current. 220 ma v dd2.5 = 2.7v, outputs unloaded. rclk[31:0]= tclk[31:0]= 2.048 mhz. rmvck[3:0] and tmvck[3:0] tied low. rmv8dc and tmv8dc tied low. note 4. i ddop operating current. 300 ma v dd2.5 = 2.7v, outputs unloaded. rclk[2:0] = tclk[2:0] = 51.84 mhz. rclk[31:3], tclk[31:3], rmvck[3:0] and tmvck[3:0] tied low. rmv8dc and tmv8dc tied low. note 4. notes on d.c. characteristics: 1. input pin or bi-directional pin with internal pull-up resistor. 2. input pin or bi-directional pin without internal pull-up resistor. 3. negative currents flow into the device (sinking), positive currents flow out of the device (sourcing). 4. typical values are given as a design aid. the product is not tested to the typical values given in the data sheet.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 199 15 freedm-32a672 timing characteristics (t a = -40c to +85c, v dd3.3 = 3.0 v to 3.6v, v dd2.5 = 2.3 v to 2.7 v) table 23 ? freedm-32a672 link i nput (figure 31 to figure 34) symbol description min max units rclk[31:0] frequency (see note 3) 1.542 1.546 mhz rclk[31:0] frequency (see note 4) 2.046 2.050 mhz rclk[2:0] frequency (see note 5) 51.84 mhz rclk[31:3] frequency (see note 5) 10 mhz rclk[31:0] duty cycle 40 60 % rmvck[3:0] frequency (see note 6) 4.092 4.100 mhz rmvck[3:0] duty cycle 40 60 % rmv8dc frequency (see note 7) 16.368 16.400 mhz rmv8dc duty cycle 40 60 % rmv8fpc frequency (see note 8) 4.092 4.100 mhz rmv8fpc duty cycle 40 60 % tp mvc rmv8dc to rmv8fpc skew -10 10 ns sysclk frequency 25 45 mhz sysclk duty cycle 40 60 % ts rd rd[2:0] set-up time 1 ns th rd rd[2:0] hold time 2 ns ts rd rd[31:3] set-up time 5 ns th rd rd[31:3] hold time 5 ns ts rd_2mvip rd[31:0] set-up time (2.048 mbps h-mvip mode) 5 ns th rd_2mvip rd[31:0] hold time (2.048 mbps h-mvip mode) 5 ns ts rd_8mvip rd[31:0] set-up time (8.192 mbps h-mvip mode) 5 ns
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 200 symbol description min max units th rd_8mvip rd[31:0] hold time (8.192 mbps h-mvip mode) 5 ns ts rfpb rfpb[3:0] set-up time 50 ns th rfpb rfpb[3:0] hold time 50 ns ts rfp8b rfp8b set-up time 50 ns th rfp8b rfp8b hold time 50 ns ts tbd tbd set-up time (see note 9) 15 ns th tbd tbd hold time 0 ns notes on input timing: 1. when a set-up time is specified between an input and a clock, the set-up time is the time in nanoseconds from the 1.4 volt point of the input to the 1.4 volt point of the clock. 2. when a hold time is specified between an input and a clock, the hold time is the time in nanoseconds from the 1.4 volt point of the clock to the 1.4 volt point of the input. 3. applicable only to channelised t1/j1 links and measured between framing bits. 4. applicable only to channelised e1 links and measured between framing bytes. 5. applicable only to unchannelised links of any format and measured between any two rclk rising edges. 6. applicable only to 2.048 mbps h-mvip links and measured between any two rmvck[n] falling edges. 7. applicable only to 8.192 mbps h-mvip links and measured between any two rmv8dc falling edges. 8. applicable only to h-mvip links and measured between any two rmv8fpc falling edges. 9. tbd set-up time is measured with a 20 pf load on tbclk. the set-up time increases by typically 1 ns for each 10 pf of extra load on tbclk.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 201 figure 31 ? receive data & frame pulse timing (2.048 mbps h-mvip mode) rmvck[n] rfpb[n] ts rfpb th rfpb rd[m] ts rd_2mvip th rd_2mvip (m=8n,8n+1...8n+7) figure 32 ? receive data & frame pulse timing (8.192 mbps h-mvip mode) rmv8fpc rfp8b ts rfp8b th rfp8b rd[n] ts rd_8mvip th rd_8mvip rmv8dc tp mvc
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 202 figure 33 ? receive data timing (non h-mvip mode) rclk[n] ts rd th rd rd[n] figure 34 ? bert input timing tbclk ts tbd th tbd tbd table 24 ? freedm-32a672 link output (figure 35 to figure 38) symbol description min max units tclk[31:0] frequency (see note 4) 1.542 1.546 mhz tclk[31:0] frequency (see note 5) 2.046 2.050 mhz tclk[2:0] frequency (see note 6) 51.84 mhz tclk[31:3] frequency (see note 6) 10 mhz tclk[31:0] duty cycle 40 60 % tmvck[3:0] frequency (see note 7) 4.092 4.100 mhz tmvck[3:0] duty cycle 40 60 % tmv8dc frequency (see note 8) 16.368 16.400 mhz tmv8dc duty cycle 40 60 % tmv8fpc frequency (see note 9) 4.092 4.100 mhz tmv8fpc duty cycle 40 60 %
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 203 symbol description min max units tp mvc tmv8dc to tmv8fpc skew -10 10 ns ts tfpb tfpb[3:0] set-up time 50 ns th tfpb tfpb[3:0] hold time 50 ns ts tfp8b tfp8b set-up time 50 ns th tf8pb tfp8b hold time 50 ns t p td tclk[2:0] low to td[2:0] valid 3 12 ns t p td tclk[31:3] low to td[31:3] valid 4 25 ns t p td_2mvip tmvck[3:0] low to td[31:0] valid (2.048 mbps h-mvip mode) 4 25 ns t p td_8mvip tmv8dc low to td[31:0] valid (8.192 mbps h-mvip mode) 4 25 ns t p rbd rbclk low to rbd valid -1 5 ns notes on output timing: 1. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 2. maximum and minimum output propagation delays are measured with a 50 pf load on all the outputs, except for the td[2:0] outputs. for td[2:0] outputs, propagation delays are measured with a 20 pf load. maximum propagation delay for td[2:0] increases by typically 1 ns for each 10 pf of extra load. 3. output propagation delays of signal outputs that are specified in relation to a reference output are measured with a 50 pf load on both the signal output and the reference output. 4. applicable only to channelised t1/j1 links and measured between framing bits. 5. applicable only to channelised e1 links and measured between framing bytes. 6. applicable only to unchannelised links of any format and measured between any two tclk rising edges. 7. applicable only to 2.048 mbps h-mvip links and measured between any two tmvck[n] falling edges.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 204 8. applicable only to 8.192 mbps h-mvip links and measured between any two tmv8dc falling edges. 9. applicable only to h-mvip links and measured between any two tmv8fpc falling edges. 10. output tristate delay is the time in nanoseconds from the 1.4 volt point of the reference signal to the point where the total current delivered through the output is less than or equal to the leakage current. figure 35 ? transmit data & frame pulse timing (2.048 mbps h-mvip mode) td[m] tp td_2mvip tmvck[n] tfpb[n] ts tfpb th tfpb (m=8n,8n+1...8n+7)
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 205 figure 36 ? transmit data & frame pulse timing (8.192 mbps h-mvip mode) tmv8dc td[n] tp td_8mvip tmv8fpc tfp8b ts tfp8b th tfp8b tp mvc figure 37 ? transmit data timing (non h-mvip mode) tclk[n] tp td td[n]
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 206 figure 38 ? bert output timing rbclk tp rbd rbd table 25 ? any-phy packet interface (figure 39 to figure 40) symbol description min max units rxclk frequency 0 50 mhz rxclk duty cycle 40 60 % txclk frequency 0 50 mhz txclk duty cycle 40 60 % ts appi all appi inputs set-up time to rxclk, txclk 4 ns th appi all appi inputs hold time to rxclk, txclk 1 ns tp appi rxclk, txclk to all appi outputs valid 2 12 ns t z appi rxclk, txclk to appi outputs tristate 2 12 ns t zd appi rxclk, txclk to appi outputs driven 2 ns notes on any-phy packet interface output timing: 1. maximum and minimum output propagation delays are measured with a 100 pf load on all the outputs.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 207 figure 39 ? receive any-phy packet interface timing rxclk rpa, rsx, rval rxdata[15:0] rxprty, rerr reop, rmod rxaddr[2:0] renb ts appi th appi tp appi tz appi tzd appi rpa, rsx, rval rxdata[15:0] rxprty, rerr reop, rmod rpa, rsx, rval rxdata[15:0] rxprty, rerr reop, rmod
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 208 figure 40 ? transmit any-phy packet interface timing txclk tpan[2:0] trdy txaddr[12:0] txdata[15:0] txprty, tsx teop, tmod terr ts appi th appi tp appi tz appi tzd appi tpan[2:0] trdy tpan[2:0] trdy table 26 ? microprocessor interface read access (figure 41) symbol description min max units ts ar address to valid read set-up time 10 ns th ar address to valid read hold time 5 ns ts alr address to latch set-up time 10 ns th alr address to latch hold time 10 ns tv l valid latch pulse width 5 ns ts lr latch to read set-up 0 ns th lr latch to read hold 5 ns
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 209 symbol description min max units tp rd valid read to valid data propagation delay 40 ns tz rd valid read deasserted to output tristate 20 ns tp inth valid read deasserted to intb high 50 ns figure 41 ? microprocessor read access timing intb tp inth (csb+rdb) valid data d[15:0] tp rd tz rd ts ar th ar valid address a[11:2] ale ts alr tv l ts lr th alr th lr notes on microprocessor read timing: 1. a valid read cycle is defined as a logical or of the csb and the rdb signals.
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 210 2. microprocessor interface timing applies to normal mode register accesses only. 3. in non-multiplexed address/data bus applications, ale should be held high, parameters ts alr , th alr , tv l , ts lr , and th lr are not applicable. 4. parameter th ar is not applicable if address latching is used. table 27 ? microprocessor interface write access (figure 42) symbol description min max units ts aw address to valid write set-up time 10 ns ts dw data to valid write set-up time 20 ns ts alw address to latch set-up time 10 ns th alw address to latch hold time 10 ns tv l valid latch pulse width 5 ns ts lw latch to write set-up 0 ns th lw latch to write hold 5 ns th dw data to valid write hold time 5 ns th aw address to valid write hold time 5 ns tv wr valid write pulse width 20 ns
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 211 figure 42 ? microprocessor write access timing th dw valid data d[7:0] tv wr ts aw th aw ts dw (csb+wrb) a[7:0] valid address ale tv l ts alw ts lw th alw th lw notes on microprocessor write timing: 1. a valid write cycle is defined as a logical or of the csb and the wrb signals. 2. microprocessor interface timing applies to normal mode register accesses only. 3. in non-multiplexed address/data bus architectures, ale should be held high, parameters ts alw , th alw , tv l , ts lw , and th lw are not applicable. 4. parameters th aw and ts aw are not applicable if address latching is used. table 28 ? jtag port interface (figure 43) symbol description min max units tck frequency 1 mhz tck duty cycle 40 60 % ts tms tms set-up time to tck 50 ns th tms tms hold time to tck 50 ns
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 212 symbol description min max units ts tdi tdi set-up time to tck 50 ns th tdi tdi hold time to tck 50 ns t p tdo tck low to tdo valid 2 60 ns figure 43 ? jtag port interface timing ts tms th tms tms tck ts tdi th tdi tdi tp tdo tdo tck
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 213 16 ordering and thermal information table 29 ? freedm-32a672 ordering information part no. description PM7381-PI 329 plastic ball grid array (pbga) table 30 ? freedm-32a672 thermal information part no. ambient temperature theta ja PM7381-PI -40c to +85c 25 c/w
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 214 17 mechanical information figure 44 ? 329 pin plastic ball grid array (pbga) note ? the freedm-32p672 is manufactured using the 4-layer variant of the package shown in the drawing below. 0.20 (2x) a e e 1 a1 ball corner d d 1 45 o chamfer 4 places top view b 0.20 (2x) package type : 329 plastic ball grid array - pbga body size : 31 x 31 x 2.33 mm (4 layer) dim. a (2 layer) a 1 a 2 dd 1 ee 1 ij b c (4 layer) d px py aaa bbb min. 2.12 0.50 1.12 30.80 25.50 30.80 25.50 0.60 27.84 27.84 - - nom . 2.33 0.60 1.17 31.00 26.00 31.00 26.00 1.53 1.53 0.76 0.56 1.0 27.94 27.94 - - max. 2.56 0.70 1.22 31.20 26.70 31.20 26.70 0.90 28.04 28.04 0.15 0.15 e - - 1.27 c (2 layer) 0.56 2.12 2.33 2.54 a (4 layer) - - - - -- -- - - a 2 a a 1 seating plane c side view bbb c aaa c c 30 o typ +/- 1 o a1 ball corner bottom view "d" dia. 3 places j i e b a b c d e f g h j k l m n p r t u v w y aa ab ac py px 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 21 23 22 e notes: 1) all dimensions in millimeter. 2) dimension aaa denotes coplanarity. 3) dimension bbb denotes parallel. a1 ball indicator
pm7381 freedm-32a672 datasheet pmc-1990263 issue 6 32 link, 672 channel frame engine and dat a link manager with any-phy packet interface none of the information contained in this doc ument constitutes an express or implied warranty by pmc-sierra, inc. as to the suf ficiency, fitness or suitability for a particular purpose of any su ch information or the fitness, or su itability for a particular purpose, merchanta bility, performance, compatibility with other parts or systems, of any of the products of pmc-sierra, inc., or any portion thereof, referred to in t his document. pmc-sierra, inc. expressly disclaims all representations and wa rranties of any kind regarding the contents or use of the inform ation, including, but not limited to, express and implied warranties of accuracy, completeness, merchantability, fitness for a particular use, or non-inf ringement. in no event will pmc-sierra, inc. be liable for any direct, i ndirect, special, incidental or consequential damages, including, but not limited to, lost profits, lost business or lost data resulting from any use of or reli ance upon the information, whether or not pmc-sierra, inc. has been advised of the possibility of such damage. freedm is a trademark of pmc-sierra, inc. the technology discussed is protected by one or more of the following patents: u.s. patent nos. 5,640,398 and 6,188,699 can. patent no. 2,161,921 relevant patent applications and other patents may also exist. ? 2001 pmc-sierra, inc pmc-1990263 (r6) issue date: august 2001 pmc-sierra, inc. 8555 baxter place burnaby, bc canada v5a 4v7 604 .415.6000 contacting pmc-sierra, inc. pmc-sierra, inc. 8555 baxter place burnaby, bc canada v5a 4v7 tel: (604) 415-6000 fax: (604) 415-6200 document information: document@pmc-sierra.com corporate information: info@pmc-sierra.com application information: apps@pmc-sierra.com web site: http://www.pmc-sierra.com

▲Up To Search▲

Price & Availability of PM7381-PI

	To Download PM7381-PI Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .